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
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1060380
Description of problem:
kernel: sssd_nss[15721]: segfault at 94 ip 0000003124024fbc sp 00007fff401c4070
error 4 in libdbus-1.so.3.4.0[3124000000+40000]
Version-Release number of selected component (if applicable):
sssd-1.9.2-129.el6_5.4.x86_64
How reproducible:
unknown
Steps to Reproduce:
1.N/A
Actual results:
sssd_nss segfaults
Expected results:
no segfaults
Additional info:
will also provide coredump, bt and sosreport
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/2245
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1060380
Comments
Comment from dpal at 2014-02-13 15:25:47
Fields changed
blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
milestone: NEEDS_TRIAGE => SSSD 1.11.5
review: True => 0
selected: =>
testsupdated: => 0
Comment from jhrozek at 2014-04-03 19:41:52
The issue is still being investigated downstream, moving to 1.11.6
milestone: SSSD 1.11.5 => SSSD 1.11.6
Comment from jhrozek at 2014-05-15 13:55:51
It turned out the crash was caused by sssd_be being restarted during enumeration. We suggested to raise the timeout as a workaround.
The proper fix is to improve enumeration performance, which is tracked in ticket #1729.
resolution: => duplicate
status: new => closed
Comment from jhrozek at 2014-09-25 08:43:00
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1123291 (Red Hat Enterprise Linux 6)
rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=1060380 1060380] => [https://bugzilla.redhat.com/show_bug.cgi?id=1060380 1060380], [https://bugzilla.redhat.com/show_bug.cgi?id=1123291 1123291]
Comment from jhrozek at 2017-02-24 15:05:55
Metadata Update from @jhrozek:
The text was updated successfully, but these errors were encountered: