Package: sssd Version: 1.50.0-2 Severity: grave I updated my stretch system this morning which led to it failing to reach a login prompt; the system would start up and then avahi-daemon, ModemManager and NetworkManager would all fail to start, then systemd-logind would fail. This repeated in a continuous loop. Initially suspecting ModemManager or NetworkManager I tried removing them (the machine has wired ethernet, configured via /etc/network/interfaces), but this did not help.
Looking at the errors provided by systemd in my logs led me to: https://lists.debian.org/debian-user/2017/02/msg00025.html which provided the clue I needed to try downgrading ssd from 1.15.0-2 (which was pulled in by the update this morning) to 1.14.2-1 (the previously installed version). The machine subquently rebooted cleanly. A coworker's machine was similiarly affected, and the same solution worked there. There seems to be a lack of errors in logs relating to sssd, but I can try to provide any extra information that might be helpful. In particular daemon.log contained many, many instances of: apus systemd[1]: Looping too fast. Throttling execution a little. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sssd depends on: ii python-sss 1.14.2-1 ii sssd-ad 1.14.2-1 ii sssd-common 1.14.2-1 ii sssd-ipa 1.14.2-1 ii sssd-krb5 1.14.2-1 ii sssd-ldap 1.14.2-1 ii sssd-proxy 1.14.2-1 sssd recommends no packages. sssd suggests no packages. -- no debconf information
