misleading error message when /var/lib/sss/db/config.ldb can't be opened

[sssd-bot]

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/427

• Created at 2010-03-19 00:39:07 by amcnabb
• Closed as Fixed
• Assigned to jhrozek

---

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.

Comments

---

Comment from sgallagh at 2010-03-19 12:38:35

Agreed. This needs to be fixed in 1.1.

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

---

Comment from sgallagh at 2010-03-22 21:23:39

Fixed by c20aad9 and e16c6e3

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

---

Comment from dpal at 2012-01-19 02:41:53

Fields changed

rhbz: => 0

---

Comment from amcnabb at 2017-02-24 14:46:11

Metadata Update from @amcnabb:

• Issue assigned to jhrozek
• Issue set to the milestone: SSSD 1.1