I can reproduce this on a local 24.04 system:
# journalctl -b -g sssd
Mär 26 17:25:56 abaconcy systemd[1]: sssd-nss.socket: Bound to unit
sssd.service, but unit isn't active.
Mär 26 17:25:56 abaconcy systemd[1]: Dependency failed for sssd-nss.socket -
SSSD NSS Service responder socket.
Mär 26 17:25:56 abaconcy systemd[1]: sssd-nss.socket: Job sssd-nss.socket/start
failed with result 'dependency'.
[...]
# 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-03-26 17:25:56 CET; 1 month 25
days ago
But, as Robie stated in comment #3 this is expected behavior. The
service or socket are not actually failing, but rather saying
"inactive". Which essentially means it stays disabled until someone
places proper configuration.
Would it be installed in a "disabled" state a simple placement would not
be enough, but it would rather need to be "enabled" manually as well.
Doing that would most probably have unexpected side-effects. This
behavior might be intentional by the upstream maintainers.
Would you mind raising a bug report with them at
https://tracker.debian.org/pkg/sssd ?
I'm keeping the bug as "Incomplete" until we know more about upstream's
intentions.
** Changed in: sssd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048436
Title:
four Dependency failed for SSSD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2048436/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
