I finally had some time to do some investigation on this bug. I appreciate the analysis done by others, and the patch provided by Dimitri.
I verified that using ConditionPathExists on sssd.service does prevent sssd from starting (as expected), which means that the error messages in the log are gone. sssd has a lot of services and socket-activated units associate with it, but all of them are ultimately bound (via systemd's BindsTo and After directives) to sssd.service, which means that they will not start unless sssd.service also starts. As such, and to avoid redundancy, I think it is better to modify only sssd.service. This has the "downside" that the user will still see warning messages (not errors) in the logs, like: Dec 09 18:44:29 focal-desktop systemd[1]: sssd-nss.socket: Bound to unit sssd.service, but unit isn't active. Dec 09 18:44:29 focal-desktop systemd[1]: Dependency failed for SSSD NSS Service responder socket. Dec 09 18:44:29 focal-desktop systemd[1]: sssd-nss.socket: Job sssd-nss.socket/start failed with result 'dependency'. Dec 09 18:44:29 focal-desktop systemd[1]: sssd-autofs.socket: Bound to unit sssd.service, but unit isn't active. Dec 09 18:44:29 focal-desktop systemd[1]: Dependency failed for SSSD AutoFS Service responder socket. Dec 09 18:44:29 focal-desktop systemd[1]: sssd-autofs.socket: Job sssd-autofs.socket/start failed with result 'dependency'. Dec 09 18:44:29 focal-desktop systemd[1]: sssd-pac.socket: Bound to unit sssd.service, but unit isn't active. Dec 09 18:44:29 focal-desktop systemd[1]: Dependency failed for SSSD PAC Service responder socket. Dec 09 18:44:29 focal-desktop systemd[1]: sssd-pac.socket: Job sssd-pac.socket/start failed with result 'dependency'. Dec 09 18:44:29 focal-desktop systemd[1]: sssd-pam-priv.socket: Bound to unit sssd.service, but unit isn't active. Dec 09 18:44:29 focal-desktop systemd[1]: Dependency failed for SSSD PAM Service responder private socket. Dec 09 18:44:29 focal-desktop systemd[1]: Dependency failed for SSSD PAM Service responder socket. Dec 09 18:44:29 focal-desktop systemd[1]: sssd-pam.socket: Job sssd-pam.socket/start failed with result 'dependency'. Dec 09 18:44:29 focal-desktop systemd[1]: sssd-pam-priv.socket: Job sssd-pam-priv.socket/start failed with result 'dependency'. Dec 09 18:44:29 focal-desktop systemd[1]: sssd-ssh.socket: Bound to unit sssd.service, but unit isn't active. Dec 09 18:44:29 focal-desktop systemd[1]: Dependency failed for SSSD SSH Service responder socket. Dec 09 18:44:29 focal-desktop systemd[1]: sssd-ssh.socket: Job sssd-ssh.socket/start failed with result 'dependency'. Dec 09 18:44:29 focal-desktop systemd[1]: sssd-sudo.socket: Bound to unit sssd.service, but unit isn't active. Dec 09 18:44:29 focal-desktop systemd[1]: Dependency failed for SSSD Sudo Service responder socket. Dec 09 18:44:29 focal-desktop systemd[1]: sssd-sudo.socket: Job sssd-sudo.socket/start failed with result 'dependency'. I think this is fine, though, because, as I said above, these are just warnings. I am going to prepare an upload with the systemd change mentioned above, and will perform more tests to verify that everything works OK. Hopefully I will be able to upload a fix to Hirsute until this Friday, and prepare an SRU for Groovy next week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900642 Title: sssd won't start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1900642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
