sssd ldap be goes into "Backend is offline" at boot because sssd isn't when resolv.conf changes


My department has run into a problem with openSuSE Leap 15.1, LDAP and sssd. In short, it appears that sssd starts prior to DHCP obtaining an IP address for the network interface. At that point, sssd ldap be goes into the “Backend is offline” state and never recovers. It appears to never recover, because it is never informed by inotify when a DHCP address is obtained and resolv.conf is updated. Consequently, a console login followed by a “systemctl restart sssd.service” is required or a reboot before non-local users can login.

Some Ubuntu users have run into the same problem:

I’ve modified our sssd.service file and placed it in /etc/systemd/system to override the default file in /usr/lib/systemd/system:

Description=System Security Services Daemon

SSSD must be running before we permit user sessions <================================================ Added this line
Before=systemd-user-sessions.service <======================== Added “” <=============================================== Added this line

ExecStart=/usr/sbin/sssd -i ${DEBUG_LOGGER}


Note that this is a workaround and not a fix.

We are using wicked.

So far, this is reproducible with desktop computers running openSuSE 15.1 using DHCP, sssd and an LDAP backend for authentication.

Was wondering if anyone else has encountered this problem and if there might be a fix forthcoming?


You need to open bug report.

Although a “fix” might require a certain amount of testing,
I’d consider what you did more of a fix than a workaround… pretty much how I’d have modified the Unit file.

Congrats on working it out.
And yes… pls also submit a bug report with your configuration.


Hello Trevor,

we run the same situation here. There is an open bug report for this: 1136139 – sssd ad/ldap domain are offline after first boot (cannot resolv srv _ldap._srv)

Best regards