#2980 sssd_be[11010]: segfault at 0 ip 00007ff889ff61bb sp 00007ffc7d66a3b0 error 4 in libsss_ipa.so[7ff889fcf000+5d000]
Closed: Fixed None Opened 5 years ago by lslebodn.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1322458

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem:
 - Each night, SSSD will segfault (SIGSEV)

Version-Release number of selected component (if applicable):
 - sssd-common-1.13.0-40.el7_2.1

How reproducible:
 - Most of the time

Steps to Reproduce:
1. Wait until around 7pm EST

Actual results:
 - sssd_be[25928]: segfault at 0 ip 00007fa2a92241bb sp 00007ffe132b0bf0 error
4 in libsss_ipa.so[7fa2a91fd000+5d000]

Expected results:
 - No segfault

Additional info:

Lukas believes that a NULL check would solve the bug and since this is a crash, I'm filing the ticket into 1.13.4.

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
milestone: NEEDS_TRIAGE => SSSD 1.13.4
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

owner: somebody => lslebodn
patch: 0 => 1
status: new => assigned



resolution: => fixed
status: assigned => closed

Metadata Update from @lslebodn:
- Issue assigned to lslebodn
- Issue set to the milestone: SSSD 1.13.4

4 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/4021

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.