Red Hat Bugzilla – Bug 1086264
sssd hangs on restart and sssd_be consumes 100% cpu on s390x and ppc64 archs
Last modified: 2014-10-14 00:48:23 EDT
Description of problem: sssd hangs on restart and sssd_be consumes 100% cpu Version-Release number of selected component (if applicable): sssd-1.9.2-129.el6 How reproducible: Very often on ppc64 and s390x archs Steps to Reproduce: 1. sssd.conf has [sssd] config_file_version = 2 services = nss, pam domains = sssdad2012.com [domain/sssdad2012.com] id_provider = ad auth_provider = ad ad_domain = sssdad2012.com ad_server = kauwin.sssdad2012.com 2. Restart sssd Actual results: sssd_be consumes 100% cpu and restart hangs. Expected results: Additional info:
Kaushik, could you please try if killing the sssd_be process (kill -SEGV $(pidof sssd_be)) still hangs the process with 1.11 ?
Tested on RHEL6.6 with sssd version 1.11.5.1-1.el6.ppc64 I added a (kill -SEGV $(pidof sssd_be) in the automation script. But sssd seems to recover from this forced
(In reply to Kaushik Banerjee from comment #3) > Tested on RHEL6.6 with sssd version 1.11.5.1-1.el6.ppc64 > > I added a (kill -SEGV $(pidof sssd_be) in the automation script. But sssd > seems to recover from this forced Then I would propose to either fix this bug or mark is as fixed with the rebase. I remember a couple of fixes upstream that were arch-specific (the bool/dbus_bool_t issue comes to mind). Thank you for testing!
I meant to say 'close' this bug instead of 'fix' earlier. Per comment #3 the recovery is fixed in 1.11. Kauhshik, can you qa_ack this bug since you alredy amended the automation? Then I would include the bug in the 6.6 errata.
This was fixed in a rebase.
*** Bug 1102874 has been marked as a duplicate of this bug. ***
Verified with sssd-1.11.6-1.el6.ppc64 sssd recovers from a forced crash.
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/RHBA-2014-1375.html