Environment
Situation
sssd on SLES 12 SP2 with NAM 4.2.2 working fine. After upgrading to NAM 4.4 which comes with eDirectory 9.0.3, sssd fails to start.
44sles12sp2:~ # systemctl status sssd
? sssd.service - System Security Services Daemon
Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2017-09-14 13:45:43 +08; 18min ago
Process: 3428 ExecStart=/usr/sbin/sssd -D -f (code=exited, status=1/FAILURE)
Sep 14 13:45:42 44sles12sp2 sssd[3436]: Starting up
Sep 14 13:45:42 44sles12sp2 sssd[3435]: Starting up
Sep 14 13:45:42 44sles12sp2 sssd[3437]: Starting up
Sep 14 13:45:42 44sles12sp2 sssd[3438]: Starting up
Sep 14 13:45:43 44sles12sp2 sssd[be[3439]: Starting up
Sep 14 13:45:43 44sles12sp2 sssd[3431]: Exiting the SSSD. Could not restart critical service [karthi-edir].
Sep 14 13:45:43 44sles12sp2 systemd[1]: sssd.service: Control process exited, code=exited status=1
Sep 14 13:45:43 44sles12sp2 systemd[1]: Failed to start System Security Services Daemon.
Sep 14 13:45:43 44sles12sp2 systemd[1]: sssd.service: Unit entered failed state.
Sep 14 13:45:43 44sles12sp2 systemd[1]: sssd.service: Failed with result 'exit-code'.
44sles12sp2:~ # systemctl start sssd
Job for sssd.service failed because the control process exited with error code. See "systemctl status sssd.service" and "journalctl -xe" for details
Resolution
This is a bug and below workaround could be used to address it.
a. Remove /etc/ld.so.conf.d/ice.conf or comment out the line in the file.
b. Run #ldconfig –v
c. Now start sssd: #systemctl start sssd
sssd starts without any issues.