@ahasenack: Even in case things "work", I observe the following: Jun 11 14:41:15 cip000 systemd[1]: Starting System Security Services Daemon... Jun 11 14:41:24 cip000 sssd[920]: Starting up Jun 11 14:41:25 cip000 sssd[be[998]: Starting up Jun 11 14:41:28 cip000 sssd[1021]: Starting up Jun 11 14:41:28 cip000 sssd[1022]: Starting up Jun 11 14:41:29 cip000 systemd[1]: Started System Security Services Daemon. Jun 11 14:42:38 cip000 sssd[be[998]: Backend is online
Users trying to log in between 14:41 and 14:42 get an error message. In the logfiles, I only see tons of: (Mon Jun 11 14:42:32 2018) [sssd[nss]] [sss_dp_get_reply] (0x0010): The Data Provider returned an error [org.freedesktop.sssd.Error.DataProvider.Offline] in the nss-logs, and a few: (Mon Jun 11 14:41:49 2018) [sssd[pam]] [sss_dp_get_reply] (0x0010): The Data Provider returned an error [org.freedesktop.sssd.Error.DataProvider.Offline] in the sssd_pam log for each failed attempt. Even though I get "Backend is online" in this case, the logs don't tell me why it actually recovered. So maybe 6 is not high enough? Is it really sufficient to enable debugging only for sssd itself, don't I need to enable it for the provider, too? Also, shouldn't this debug_level be a bitmask? In any case, network connectivity was available well before 14:42:38. I actually logged in via ssh at 14:41:52 as user, but since the backend was still offline, no kerberos ticket was initialized. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723350 Title: sssd offline on boot, stays offline forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1723350/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
