Systemd do not respawn sssd on failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sssd (Ubuntu) |
Fix Released
|
Undecided
|
Andreas Hasenack |
Bug Description
The sssd crashed recently (probably due to lack of free memory, other process was killed by OOM same time). However automated respawn was not performed because it was not configured in systemd unit file.
$ lsb_release -rd
Description: Ubuntu 16.04.5 LTS
Release: 16.04
brudas@hqv074:~$ apt-cache policy sssd
$ apt-cache policy sssd
sssd:
Installed: 1.13.4-1ubuntu1.12
Candidate: 1.13.4-1ubuntu1.12
Version table:
*** 1.13.4-1ubuntu1.12 500
500 http://
100 /var/lib/
1.
500 http://
1.
500 http://
$ cat /lib/systemd/
[Unit]
Description=System Security Services Daemon
# SSSD must be running before we permit user sessions
Before=
Wants=nss-
[Service]
ExecStart=
Type=notify
NotifyAccess=main
PIDFile=
[Install]
WantedBy=
Expected behavior: systemd attempts to restart the service
Thank you.
Related branches
- Bryce Harrington (community): Approve
- Canonical Server packageset reviewers: Pending requested
-
Diff: 119 lines (+78/-1)2 files modifieddebian/changelog (+76/-0)
debian/control (+2/-1)
- Christian Ehrhardt (community): Approve
- Bryce Harrington (community): Approve
- Canonical Server: Pending requested
-
Diff: 175 lines (+112/-3)5 files modifieddebian/changelog (+64/-0)
debian/control (+4/-3)
debian/patches/python3-shebang.patch (+13/-0)
debian/patches/restart-on-failure.patch (+29/-0)
debian/patches/series (+2/-0)
tags: | added: server-triage-discuss |
tags: | removed: server-triage-discuss |
Changed in sssd (Ubuntu): | |
status: | Confirmed → In Progress |
assignee: | nobody → Andreas Hasenack (ahasenack) |
Status changed to 'Confirmed' because the bug affects multiple users.