Package: sssd Version: 2.2.0-3 Severity: grave Justification: renders package unusable
After upgrading to 2.2.0-3, sssd will not start (automatically). There are two failure modes, both likely related to #886483 I reported over a year ago. First failure mode happens if any services are listed in sssd.conf like (any service here will cause failure) service = pam, nss Startig sssd with systemctl will now (correctly) start the listed services, BUT it will also insist on trying to start the corresponding socket listener, which times out trying to get the socket, eventually causing systemd to kill the whole stack of processes, leaving no sssd processes running. It is, however, possible to start sssd manually from command line: "sssd -i" works as expected. Second failure mode is triggered by trying the obvious: commenting out the whole "service" line from sssd.conf. However, now sssd fails both from command line and from systemd because "sssd: SSSD couldn't load the configuration database [22]: Invalid argument." There does not seem to be any way of disabling all non-socket services but if at least one non-socket service is active, systemd will time out trying to load the corresponding socket. I even removed every .socket file related to sssd from my systemd but it didn't help (yes, I did a daemon-reexec and daemon-reload). Only fix I managed to find is a downgrade to 1.16.3-3.1. Cheers, Juha -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)