Socket activation of SSSD doesn't work and leads to chaos

[sssd-bot]

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/3298

• Created at 2017-02-03 13:41:04 by stricumu
• Closed at 2017-03-01 12:05:47 as Fixed
• Assigned to fidencio

---

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.

fidencio 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.

Comments

---

Comment from fidencio at 2017-02-03 13:43:01

Fields changed

owner: somebody => fidencio

---

Comment from stricumu at 2017-02-03 13:47:06

Using 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 with ldaps+autofs based one.

---

Comment from stricumu at 2017-02-03 14:05:45

Debian bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854048

---

Comment from fidencio at 2017-02-04 00:00:03

Fields changed

patch: 0 => 1

---

Comment from fidencio at 2017-02-04 00:00:22

PR: #142

---

Comment from fidencio at 2017-02-04 17:00:57

PR has been NACK on IRC.

---

Comment from fidencio at 2017-02-04 17:01:12

Fields changed

patch: 1 => 0
status: new => assigned

---

Comment from fidencio at 2017-02-05 14:02:35

PR: #143

---

Comment from fidencio at 2017-02-05 14:03:26

Fields changed

patch: 0 => 1

---

Comment from jhrozek at 2017-02-10 10:11:43

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.15.1

---

Comment from jhrozek at 2017-02-22 18:03:28

Fields changed

rhbz: => 0

---

Comment from stricumu at 2017-02-24 14:53:09

Metadata Update from @StricUmu:

• Issue assigned to fidencio
• Issue set to the milestone: SSSD 1.15.1

---

Comment from lslebodn at 2017-03-01 12:05:23

master:

• bd5e09b
• 0adcf95

---

Comment from lslebodn at 2017-03-01 12:05:29

Metadata Update from @lslebodn:

• Custom field component reset
• Custom field design_review reset
• Custom field mark reset
• Custom field patch adjusted to on (was: 1)
• Custom field review reset
• Custom field sensitive reset
• Custom field testsupdated reset
• Custom field type reset
• Custom field version reset
• Issue close_status updated to: None

---

Comment from lslebodn at 2017-03-01 12:05:51

Metadata Update from @lslebodn:

• Custom field design_review reset
• Custom field mark reset
• Custom field review reset
• Custom field sensitive reset
• Custom field testsupdated reset
• Issue close_status updated to: Fixed
• Issue status updated to: Closed (was: Open)