Thanks for describing this workaround, Shane!
What I see when trying to reproduce this on 24.04:
$ apt install sssd
[...]
Setting up libpam-sss:amd64 (2.9.4-1.1ubuntu6.2) ...
Setting up sssd-common (2.9.4-1.1ubuntu6.2) ...
Creating SSSD system user & group...
warn: The home directory `/var/lib/sss' already exists. Not touching this
directory.
warn: Warning: The home directory `/var/lib/sss' does not belong to the user
you are currently creating.
Warning: found usr.sbin.sssd in /etc/apparmor.d/force-complain, forcing
complain mode
Warning from /etc/apparmor.d/usr.sbin.sssd (/etc/apparmor.d/usr.sbin.sssd line
63): Caching disabled for: 'usr.sbin.sss
d' due to force complain
Created symlink /etc/systemd/system/sssd.service.wants/sssd-autofs.socket →
/usr/lib/systemd/system/sssd-autofs.socket.
Created symlink /etc/systemd/system/sssd.service.wants/sssd-nss.socket →
/usr/lib/systemd/system/sssd-nss.socket.
Created symlink /etc/systemd/system/sssd.service.wants/sssd-pam-priv.socket →
/usr/lib/systemd/system/sssd-pam-priv.soc
ket.
Created symlink /etc/systemd/system/sssd.service.wants/sssd-pam.socket →
/usr/lib/systemd/system/sssd-pam.socket.
Created symlink /etc/systemd/system/sssd.service.wants/sssd-ssh.socket →
/usr/lib/systemd/system/sssd-ssh.socket.
Created symlink /etc/systemd/system/sssd.service.wants/sssd-sudo.socket →
/usr/lib/systemd/system/sssd-sudo.socket.
Created symlink /etc/systemd/system/multi-user.target.wants/sssd.service →
/usr/lib/systemd/system/sssd.service.
sssd-autofs.service is a disabled or a static unit, not starting it.
sssd-nss.service is a disabled or a static unit, not starting it.
sssd-pam.service is a disabled or a static unit, not starting it.
sssd-ssh.service is a disabled or a static unit, not starting it.
sssd-sudo.service is a disabled or a static unit, not starting it.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 148.
Setting up sssd-proxy (2.9.4-1.1ubuntu6.2) ...
Setting up sssd-ad-common (2.9.4-1.1ubuntu6.2) ...
Created symlink /etc/systemd/system/sssd.service.wants/sssd-pac.socket →
/usr/lib/systemd/system/sssd-pac.socket.
sssd-pac.service is a disabled or a static unit, not starting it.
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 148.
Setting up sssd-krb5-common (2.9.4-1.1ubuntu6.2) ...
Setting up sssd-krb5 (2.9.4-1.1ubuntu6.2) ...
Setting up sssd-ldap (2.9.4-1.1ubuntu6.2) ...
Setting up sssd-ad (2.9.4-1.1ubuntu6.2) ...
Setting up sssd-ipa (2.9.4-1.1ubuntu6.2) ...
Setting up sssd (2.9.4-1.1ubuntu6.2) ...
So it's a similar "is a disabled or a static unit, not starting it" error
message. In addition to "Could not execute systemctl: at
/usr/bin/deb-systemd-invoke line 148".
Also:
$ systemctl status sssd-nss.socket
○ sssd-nss.socket - SSSD NSS Service responder socket
Loaded: loaded (/usr/lib/systemd/system/sssd-nss.socket; enabled; preset:
enabled)
Active: inactive (dead)
Triggers: ● sssd-nss.service
Docs: man:sssd.conf(5)
Listen: /var/lib/sss/pipes/nss (Stream)
Jun 18 14:07:34 adsf systemd[1]: sssd-nss.socket: Job sssd-nss.socket/start
failed with result 'dependency'.
Jun 18 14:07:34 adsf systemd[1]: sssd-nss.socket: Bound to unit sssd.service,
but unit isn't active.
Jun 18 14:07:34 adsf systemd[1]: Dependency failed for sssd-nss.socket - SSSD
NSS Service responder socket.
Jun 18 14:07:34 adsf systemd[1]: sssd-nss.socket: Job sssd-nss.socket/start
failed with result 'dependency'.
Jun 18 14:07:34 adsf systemd[1]: sssd-nss.socket: Bound to unit sssd.service,
but unit isn't active.
Jun 18 14:07:34 adsf systemd[1]: Dependency failed for sssd-nss.socket - SSSD
NSS Service responder socket.
Jun 18 14:07:34 adsf systemd[1]: sssd-nss.socket: Job sssd-nss.socket/start
failed with result 'dependency'.
Jun 18 14:07:34 adsf systemd[1]: sssd-nss.socket: Bound to unit sssd.service,
but unit isn't active.
Jun 18 14:07:34 adsf systemd[1]: Dependency failed for sssd-nss.socket - SSSD
NSS Service responder socket.
Jun 18 14:07:34 adsf systemd[1]: sssd-nss.socket: Job sssd-nss.socket/start
failed with result 'dependency'.
But even after installing freeipa-client and running ipa-client-install I don't
see any sssd.conf config file:
$ tree /etc/sssd/
/etc/sssd/
└── conf.d
2 directories, 0 files
Interesting, sssd.service does not start due to missing config file
Conditions, and therefore blocking sssd-nss.socket:
$ systemctl status sssd
○ sssd.service - System Security Services Daemon
Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; preset:
enabled)
Active: inactive (dead)
Condition: start condition unmet at Wed 2025-06-18 14:14:29 UTC; 3s ago
├─ ConditionPathExists=|/etc/sssd/sssd.conf was not met
└─ ConditionDirectoryNotEmpty=|/etc/sssd/conf.d was not met
Shane, was that config file created manually on your end?
** Changed in: sssd (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838680
Title:
socket activation services fail to start with no config file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1838680/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
