#427 misleading error message when /var/lib/sss/db/config.ldb can't be opened
Closed: Fixed None Opened 14 years ago by amcnabb.

If sssd can't write to /var/lib/sss/db/config.ldb, it prints the error, "Cannot read config file /etc/sssd/sssd.conf, please check if permissions are 0600 and the file is owned by root.root". I tracked this down by doing strace; here's the last few lines:

[pid  1642] stat("/var/lib/sss/db/config.ldb", 0x7fffaa441500) = -1 ENOENT (No such file or directory)
[pid  1642] open("/var/lib/sss/db/config.ldb", O_RDWR|O_CREAT, 0666) = -1 EROFS (Read-only file system)
[pid  1642] write(3, "[sssd] [confdb_init] (0): ", 26) = 26
[pid  1642] write(3, "Unable to open config database ["..., 60) = 60
[pid  1642] close(4)                    = 0
[pid  1642] write(3, "[sssd] [load_configuration] (0):"..., 33) = 33
[pid  1642] write(3, "The confdb initialization failed"..., 33) = 33
[pid  1642] write(2, "Cannot read config file /etc/sss"..., 117Cannot read config file /etc/sssd/sssd.conf, please check if permissions are 0600 and the file is owned by root.root
) = 117

I think there should be a separate error message if /var/lib/sss/db/config.ldb can't be opened.


Agreed. This needs to be fixed in 1.1.

milestone: NEEDS_TRIAGE => SSSD 1.1
owner: somebody => jhrozek
priority: major => critical

Fixed by c20aad9 and e16c6e3

fixedin: => 1.1.0
resolution: => fixed
status: new => closed
tests: 0 => 1

Fields changed

rhbz: => 0

Metadata Update from @amcnabb:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.1

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1469

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata