sssd_be[11010]: segfault at 0 ip 00007ff889ff61bb sp 00007ffc7d66a3b0 error 4 in libsss_ipa.so[7ff889fcf000+5d000]

[sssd-bot]

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/2980

• Created at 2016-03-30 17:57:10 by lslebodn
• Closed as Fixed
• Assigned to lslebodn
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1322458

---

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
2.
3.

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:

Comments

---

Comment from jhrozek at 2016-04-01 10:41:13

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

---

Comment from lslebodn at 2016-04-11 15:01:56

Fields changed

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

---

Comment from lslebodn at 2016-04-12 23:27:59

master:

• 22eead9

sssd-1-13:

• 3b2c92f

resolution: => fixed
status: assigned => closed

---

Comment from lslebodn at 2017-02-24 14:26:18

Metadata Update from @lslebodn:

• Issue assigned to lslebodn
• Issue set to the milestone: SSSD 1.13.4