Sles12SP5 - Issue with SystemSecurityServiceDaemon / SSSD

SUSE Linux Enterprise Server SLES Updates
1

Hello all,

we have got some trouble with the new Sles12 ServicePack5.
we have several Sles12SP4 (over 100) servers which are set up with ldap with the SSSD. After the ServicePack Migration from Sles12SP4 to Sles12SP5 the SSSD service does not start any more. Also a complete new server from the scratch Sles12Sp5 with a fresh sssd installation do not let me start the service anymore. At the Moment i have my four test servers and i try to get the SSSD service starting but i am running out of ideas…

Have you go any Idea what i can try?

Dec 16 11:25:33 Server01 systemd[1]: Starting System Security Services Daemon…
Dec 16 11:25:33 Server01 sssd[12392]: NSCD socket was detected and seems to be configured to cache some of the databases controlled by SSSD [passwd,group,netgroup,services]. It is recommended not to run NSCD in parallel with SSSD, unless NSCD is configured not to cache these.
Dec 16 11:25:33 Server01 sssd[12392]: Starting up
Dec 16 11:25:33 Server01 systemd[1]: sssd.service: Main process exited, code=dumped, status=11/SEGV
Dec 16 11:25:33 Server01 systemd[1]: Failed to start System Security Services Daemon.
Dec 16 11:25:33 Server01 systemd[1]: sssd.service: Unit entered failed state.
Dec 16 11:25:33 Server01 systemd[1]: sssd.service: Failed with result ‘core-dump’.
Dec 16 11:25:34 Server01 systemd-coredump[12393]: Process 12392 (sssd) of user 0 dumped core.

Greetings and some nice holidays!
Patrick

2

Hi Patrick

This bug was found too late in the RC phase of SLES 12 SP5 to make it into the shipping media.

However, the fix (in sssd-1.16.1-7.2.1) was released a few days ago.
It is published in the update channels and here : https://download.suse.com/patch/finder/#bu=suse&familyId=7261&productId=65832&dateRange=&startDate=&endDate=&priority=&architecture=&keywords=sssd&xf=7261&xp=7261_65832

Best regards
Andreas

3

Hello Andreas,
Thanks for you quick response!

Greetings
Patrick