RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 861075 - SSSD_NSS failure to gracefully restart after sbus failure
Summary: SSSD_NSS failure to gracefully restart after sbus failure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jakub Hrozek
QA Contact: Kaushik Banerjee
URL:
Whiteboard:
Depends On:
Blocks: 881827
TreeView+ depends on / blocked
 
Reported: 2012-09-27 13:11 UTC by Dmitri Pal
Modified: 2020-05-02 16:59 UTC (History)
3 users (show)

Fixed In Version: sssd-1.9.2-24.el6
Doc Type: Bug Fix
Doc Text:
Cause: When sssd_be process was unwillingly terminated, SSSD responder processes failed to reconnect in case the attempt was performed before sssd_be was ready. This caused the responder to be restarted. The responder might get restarted several times before sssd_be is ready, hitting a maximum number of restarts threshold and than is was terminated completely. Consequence: SSSD responder is not gracefully restarted. Fix: Each restart of SSSD responder process is done with increasing delay. Result: sssd_be process has now enough time to recover before a responder is restarted.
Clone Of:
Environment:
Last Closed: 2013-02-21 09:37:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 2570 0 None None None 2020-05-02 16:59:20 UTC
Red Hat Product Errata RHSA-2013:0508 0 normal SHIPPED_LIVE Low: sssd security, bug fix and enhancement update 2013-02-20 21:30:10 UTC

Description Dmitri Pal 2012-09-27 13:11:31 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/1528

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.
Comment 2 Kaushik Banerjee 2013-02-01 14:11:59 UTC 
Verified as SanityOnly in version 1.9.2-82 since no regressions are seen and all tests pass.
Comment 3 errata-xmlrpc 2013-02-21 09:37:19 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0508.html
Note You need to log in before you can comment on or make changes to this bug.