Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 969652
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
Description of problem: sssd_be had crashed with following error. ====================================================================== kernel: sssd_be[31907] general protection ip:7f776001c6b0 sp:7fff36bc0498 error:0 in libtevent.so.0.9.17[7f7760019000+c000] ====================================================================== Version-Release number of selected component (if applicable): sssd-client-1.9.2-82.4.el6_4.x86_64 sssd-1.9.2-82.4.el6_4.x86_64 How reproducible: Can't reproduce. The crash appeared to be onetime. Steps to Reproduce: 1. Actual results: Will attach the backtrace and core dump file. Expected results: Additional info:
Fields changed
blockedby: => blocking: => changelog: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => milestone: NEEDS_TRIAGE => SSSD 1.10.0 priority: major => critical review: True => 0 selected: => testsupdated: => 0
Under investigation in the Red Hat Bugzilla.
milestone: SSSD 1.10.0 => SSSD 1.10.1
The customer is no longer able to reproduce the crash and the corresponding Red Hat Bugzilla has been closed. We suspect that the issue was caused by dangling member attribute (which I believe is tracked elsewhere in ticket #1932)
resolution: => worksforme status: new => closed
Metadata Update from @dpal: - Issue set to the milestone: SSSD 1.10.1
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/3009
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.