#1528 SSSD_NSS failure to gracefully restart after sbus failure
Closed: Fixed None Opened 9 years ago by jraquino.

I have a reoccurring problem where sssd seems to get tripped up and is unable to restore itself. This is an intermittent problem that I am unable to delectably reproduce, so I am not sure whats causing it.

I show failures that appear to cause sssd_pam and sssd_be to restart, but it looks like sssd_nss is unable to connect back so it fails to restart.

Logs attached.

tarball of all requested (sanitized) relevant logs.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.1

Fields changed

milestone: SSSD 1.9.1 => SSSD 1.9.2

Fields changed

owner: somebody => jhrozek
status: new => assigned

Fields changed

milestone: SSSD 1.9.2 => SSSD 1.9.3

Fields changed

priority: major => critical

Fields changed

design: =>
design_review: => 0
fedora_test_page: =>
patch: 0 => 1

- master: 6b8c6e7e5815ea0ea9791064809c1923d608923a
- sssd-1-9: 3c922410f0b92a9b8556e28ff5d46ee7a59709c6

resolution: => fixed
status: assigned => closed

JR, I know this issue was hitting you in production. Would you like me to provide you with a test build? If so, what baseline?

review: => 0
selected: =>

Metadata Update from @jraquino:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.9.3

5 years ago

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/2570

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.