Learn more about these different git repos.
Other Git URLs
Hi, we (Ubuntu) got a user report about the lack of restart. The topic isn't so much the crash itself (was an OOM in this case) but that the user expected sssd trying to restart in that case. I'm not sure that would have helped too much in an OOM case, but in general it seems helpful to try to get the service back up again.
Yet OTOH I'm unsure if I'm missing other reasons that would speak against such a modification of the service files. Hence I'm filing this issue to start the discussion with the experts.
So what would your opinion be about a modification like:
--- a/src/sysv/systemd/sssd.service.in +++ b/src/sysv/systemd/sssd.service.in @@ -11,6 +11,7 @@ ExecStart=@sbindir@/sssd -i ${DEBUG_LOGGER} Type=notify NotifyAccess=main PIDFile=@pidpath@/sssd.pid +Restart=on-failure [Install] WantedBy=multi-user.target
And the same in others of ./src/sysv/systemd/sssd-* as you consider appropriate.
./src/sysv/systemd/sssd-*
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1716574
Issue linked to Bugzilla: Bug 1716574
Metadata Update from @jhrozek: - Issue assigned to pbrezina
Upstream PR: https://github.com/SSSD/sssd/pull/847
Metadata Update from @jhrozek: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.3
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/5009
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.