You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/555
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.
Comments
Comment from sgallagh at 2010-07-27 14:56:13
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.5.0
owner: somebody => jhrozek
Comment from sgallagh at 2010-10-20 14:10:38
Fields changed
owner: jhrozek => sgallagh
Comment from sgallagh at 2010-10-20 17:51:29
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
Comment from sgallagh at 2010-11-16 22:13:46
Fields changed
status: new => assigned
Comment from sgallagh at 2010-11-19 13:33:36
Fixed by b853b13
resolution: => fixed
status: assigned => closed
Comment from dpal at 2012-01-19 02:56:43
Fields changed
rhbz: => 0
Comment from eindenbom at 2017-02-24 14:40:39
Metadata Update from @eindenbom:
The text was updated successfully, but these errors were encountered: