Hide Forgot
This description generated by Andreas from an ABRT report architecture: x86_64 cmdline: /usr/bin/python /usr/sbin/authconfig-tui component: authconfig executable: /usr/sbin/authconfig-tui kernel: 2.6.32-71.18.2.el6.x86_64 package: authconfig-6.1.4-6.el6 reason: SSSDConfig.py:1141:import_config:ParsingError release: Red Hat Enterprise Linux Server release 6.0 (Santiago) time: 1300785771 uid: 0 backtrace: SSSDConfig.py:1141:import_config:ParsingError Traceback (most recent call last): File "/usr/sbin/authconfig-tui", line 894, in <module> sys.exit(module.run()) File "/usr/sbin/authconfig-tui", line 478, in run self.readAuthInfo() File "/usr/sbin/authconfig-tui", line 329, in readAuthInfo self.info = authinfo.read(self.printError) File "/usr/share/authconfig/authinfo.py", line 922, in read info.read() File "/usr/share/authconfig/authinfo.py", line 2176, in read self.readSSSD() File "/usr/share/authconfig/authinfo.py", line 1518, in readSSSD self.sssdConfig.import_config(all_configs[CFG_SSSD].origPath) File "/usr/lib/python2.6/site-packages/SSSDConfig.py", line 1141, in import_config raise ParsingError ParsingError Local variables in innermost frame: configfile: '/etc/sssd/sssd.conf' fd: <open file '/etc/sssd/sssd.conf', mode 'r' at 0xf984b0> self: <SSSDConfig.SSSDConfig instance at 0xfd6b00>
Created attachment 486760 [details] File: backtrace
What this ParsingError exception means? How should the authconfig behave in such situation? Should it create a new config and overwrite the erroneous one?
ParsingError means exactly what it sounds like. The existing config file is formatted incorrectly. I'd need to see the original sssd.conf to identify the exact parsing error. I'm not sure it's safe to overwrite the config. Perhaps we can save a backup first, then create a new file with the defaults from authconfig? If we do this, authconfig would need to warn loudly that such a backup was made (since the config file may have had manual changes made to it). Can we please see the sssd.conf that is failing to parse?
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0931.html