Learn more about these different git repos.
Other Git URLs
On SSSD service shutdown (e.g. after receiving SIGTERM), SSSD monitor process does not wait for its children (sssd_be, sssd_pam and sssd_nss) to terminate.
As a result sssd sometimes could not restart as terminated SSSD sub-processes are still running while new SSSD instance starts up.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.5.0 owner: somebody => jhrozek
owner: jhrozek => sgallagh
I'm raising the priority on this bug. I strongly suspect now that it is the origin of https://bugzilla.redhat.com/show_bug.cgi?id=606887 reported in Fedora, where sometimes a restart of the SSSD will fail.
cc: => orion priority: major => critical
status: new => assigned
Fixed by b853b13
resolution: => fixed status: assigned => closed
rhbz: => 0
Metadata Update from @eindenbom: - Issue assigned to sgallagh - Issue set to the milestone: SSSD 1.5.0
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/1597
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.