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.
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 b853b135b9dfa315973faff706eb32aa36b5934a
resolution: => fixed
status: assigned => closed
rhbz: => 0
Metadata Update from @eindenbom:
- Issue assigned to sgallagh
- Issue set to the milestone: SSSD 1.5.0
to comment on this ticket.
Copyright © 2014-2017 Red Hat
2.90.1 — Documentation