Kodiak Firesmith via sssd-users kirjoitti 12.9.2025 klo 23.00:
On Wednesday, September 10th, 2025 at 3:42 AM, Alexey Tikhonov via sssd-
users <[email protected]> wrote:
On Tue, Sep 9, 2025 at 8:59 PM Kodiak Firesmith via sssd-users <sssd-
[email protected] <mailto:sssd-
[email protected]>> wrote:
Hi Folks,
I've observed a few times now that if anything causes sssd.service
to fail to start at boot time that at least on Ubuntu, the system
will be stuck in an infinite service restart loop during boot-up,
rendering it largely inoperable.
Is this because of
```
Before=systemd-user-sessions.service nss-user-lookup.target
...
Restart=on-abnormal
```
?
I'm inclined to drop in a systemd override to allow sssd.service
to fail more gracefully during boot and not prevent the OS from
continuing to load, but I wanted to check in with the SSSD
mindtrust about this to see if it's specifically intentional that
broken sssd.service should break boot-up (again, at least on Ubuntu).
Is it the same as upstream?
https://github.com/SSSD/sssd/blob/master/src/sysv/systemd/
sssd.service.in <https://github.com/SSSD/sssd/blob/master/src/sysv/
systemd/sssd.service.in>
Thank you for the reply!
I pulled down the Canonical source package and yep - looks like it
differs quite a bit. I'll file a bug with Canonical about it since it
looks like the upstream service would not fail the same way.
[Unit]
Description=System Security Services Daemon
# SSSD must be running before we permit user sessions
Before=systemd-user-sessions.service nss-user-lookup.target
Wants=nss-user-lookup.target
[Service]
Environment=DEBUG_LOGGER=--logger=files
EnvironmentFile=-@environment_file@
ExecStart=@sbindir@/sssd -i ${DEBUG_LOGGER}
Type=notify
NotifyAccess=main
PIDFile=@pidpath@/sssd.pid
Restart=on-failure
[Install]
WantedBy=multi-user.target
So you are on jammy/22.04. It has changed quite a bit since then, and
you'd probably benefit from
commit a049ac715a79ddfad0d67d48fc5c60408cf62127
Author: Alejandro López <[email protected]>
Date: Wed Mar 23 16:15:01 2022 +0100
systemd: only relaunch after crashes and do not retry forever
ps. the debian/ubuntu packaging uses the upstream service files
--
t
--
_______________________________________________
sssd-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
