Over the weekend sssd got a restart and failed to come back up.
Running (the suggested) journalctl -u sssd shows a pretty clear version mismatch for ldb while loading samba
Apr 08 10:04:48 joe systemd[1]: Starting System Security Services Daemon…
Apr 08 10:04:48 joe sssd[2424]: ldb: module version mismatch in …/source4/dsdb/samdb/ldb_modules/acl.c : ldb_version=1.2.4 module_version=1.2.3
Apr 08 10:04:48 joe sssd[2424]: ldb: failed to initialise module /usr/lib64/ldb/samba/acl.so : Unavailable
Apr 08 10:04:48 joe sssd[2424]: ldb: failed to initialise module /usr/lib64/ldb/samba : Unavailable
Apr 08 10:04:48 joe sssd[2424]: SSSD couldn’t load the configuration database [5]: Input/output error.
Apr 08 10:04:48 joe systemd[1]: sssd.service: Main process exited, code=exited, status=4/NOPERMISSION
Apr 08 10:04:48 joe systemd[1]: Failed to start System Security Services Daemon.
The line “ldb_version=1.2.4 module_version=1.2.3” seems to be the problem.
A side question, I’m wondering why that dependency kills sssd when I’m not using a Windows DC (or any samba).
FWIW, we’re using eDirectory 