[Pkg-sssd-devel] Bug#854048: sssd: Socket activation of SSSD doesn't work and leads to chaos

[Tomas Forsman]

Package: sssd
Version: 1.15.0-2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Updated to sssd 1.15.0-2 from sid into stretch, which is heading for stretch

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Tried rebooting.

   * What was the outcome of this action?

Errors about lots of unrelated services. Slow boot. Slow logging in.
Trouble rebooting again.

   * What outcome did you expect instead?

Working system.


I tried installing sssd 1.15.0-2 in Debian Stretch (packages from sid),
which uses socket activation. 1.14.2 without socket activation works
fine, but with socket activation - systemd is not happy at all about
lots of services. Starting up a basic image can take 5 minutes. Logging
in with root on console on a local-only machine can take a few minutes.
Examples:
Feb  3 09:16:29 test-vm systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.Accounts': Connection timed out
Feb  3 09:16:29 test-vm systemd[1]: Failed to register name: Connection timed out
Feb  3 09:16:29 test-vm systemd[1]: Failed to set up API bus: Connection timed out
Feb  3 09:16:30 test-vm systemd[1]: Failed to register Manager vtable: File exists
...
Feb  3 09:21:30 test-vm dbus[659]: [system] Failed to activate service 'org.freedesktop.ColorManager': timed out
Feb  3 09:21:30 test-vm dbus[659]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Feb  3 09:21:30 test-vm systemd-logind[1040]: Failed to enable subscription: Failed to activate service 'org.freedesktop.systemd1': timed out
Feb  3 09:21:30 test-vm systemd-logind[1040]: Failed to fully start up daemon: Connection timed out
Feb  3 09:21:30 test-vm systemd[1]: Failed to start Login Service.

This with both trivial config from
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/about-sssd.conf.html
and also an ldaps+autofs based one.


fidencio at redhat verified the problem both under Debian Stretch and some version of Fedora.

(Re)moving /etc/systemd/system/sssd.service.wants/sssd-*.socket makes the problems go away.
Replacing all of /lib/systemd/system/sssd* (type=notify) with the ones from 1.14.2 (type=forking) also makes the problems go away. 

Upstreams bug: https://fedorahosted.org/sssd/ticket/3298

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-1-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages sssd depends on:
ii  python-sss   1.15.0-2
ii  sssd-ad      1.15.0-2
ii  sssd-common  1.15.0-2
ii  sssd-ipa     1.15.0-2
ii  sssd-krb5    1.15.0-2
ii  sssd-ldap    1.15.0-2
ii  sssd-proxy   1.15.0-2

sssd recommends no packages.

sssd suggests no packages.

-- no debconf information