Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
if there is no blank line at the end of /etc/sssd/sssd.conf, sssd wont start and you get an error in /var/log/messages about "sssd: Cannot load configuration database".
Description of problem:
if there is no blank line at the end of /etc/sssd/sssd.conf, sssd wont start and you get an error in /var/log/messages about "sssd: Cannot load configuration database".
Version-Release number of selected component (if applicable):
sssd-1.8.0-32.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. ensure there is not a blank line return at the end of sssd.conf
2. attempt to restart sssd fails
Actual results:
sssd fails to restart with above error
Expected results:
sssd should restart
Additional info:
Can you paste or attach the config file that doesn't work for you?
I tried to reproduce the bug and couldn't, my test sssd.conf has no newline at the end and works just fine.
I suspect there is something else wrong with the config file.
Broken configuration file (with missing final newline) attached. The configuration is otherwise as generated by authconfig-tui.
[root@x sssd]# service sssd restart
Stopping sssd: [ OK ]
Starting sssd: Parsing errors and warnings in file: /etc/sssd/sssd.conf
Error (1) on line 37: Data is too long.
[FAILED]
This is on 6.5.
[root@x sssd]# rpm -qi sssd
Name : sssd Relocations: (not relocatable)
Version : 1.9.2 Vendor: Red Hat, Inc.
Release : 129.el6 Build Date: Wed Oct 23 01:07:15 2013
Right, as you pointed out, we finally found the cause (in #2248) upstream.
Instead of backporting the single fix, we're going to rebase ding-libs (which is the components that is responsible for loading the configuration) to a newer version that already contains this fix in RHEL-6.6
See https://bugzilla.redhat.com/show_bug.cgi?id=1069287