I can confirm this is happening after a reboot, and that a simple USR2 signal fixes it, but I wonder why sssd doesn't get itself back into online mode on its own in this case.
For example, I tried the following: - login via kerberos using pam_sss while it was online - got my ticket - kdestroy, logout - in another terminal, bring down the network on this client workstation - try go login again - login failed, and sssd log showed: (Fri Oct 13 21:23:15 2017) [sssd[pam]] [sss_dp_get_reply] (0x0010): The Data Provider returned an error [org.freedesktop.sssd.Error.DataProvider.Offline] I then brought the network back up, and after a while (a minute or less), login was working again using krb5. This shows sssd recovered from the induced "outage". The systemd unit file we are using in ubuntu comes straight from upstream. (some searching) Found these upstream tickets: https://pagure.io/SSSD/sssd/issue/3467 https://pagure.io/SSSD/sssd/issue/3294 -- 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 (artful) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1723350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
