Bug 1292456 - sssd_be AD segfaults on missing A record
sssd_be AD segfaults on missing A record
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd (Show other bugs)
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Pavel Březina
Steeve Goveas
Depends On:
  Show dependency treegraph
Reported: 2015-12-17 09:09 EST by Martin Kosek
Modified: 2016-11-04 03:14 EDT (History)
8 users (show)

See Also:
Fixed In Version: sssd-1.14.0-0.1.alpha.el7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-11-04 03:14:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Martin Kosek 2015-12-17 09:09:58 EST
This bug is created as a clone of upstream ticket:

When using sssd on CentOS 6.6 with the AD backend against a Samba 4.2 AD domain, sssd does not handle a rare failure condition; when the SRV records point at a DC but the A record for that domain controller is missing. sssd_be periodically crashes, it restarts a couple times but generally does not recover:

Dec 16 09:44:05 host kernel: sssd_be[107682]: segfault at 0 ip 00007fd12c5e018b sp 00007fffba8db420 error 4 in libsss_ad.so[7fd12c5ca000+20000]
Dec 16 09:44:05 host abrtd: Directory 'ccpp-2015-12-16-09:44:05-107682' creation detected
Dec 16 09:44:05 host abrt[107687]: Saved core dump of pid 107682 (/usr/libexec/sssd/sssd_be) to /var/spool/abrt/ccpp-2015-12-16-09:44:05-107682 (1978368 bytes)

The SIGSEGV appears to happen in sss_ldap_init_send(), src/util/sss_ldap.c:331.

Getting into this condition is rare - it's a Samba bug that I'm working on separately. The situation could probably be replicated by poisoning DNS though. My expected behavior would be to give up on this DC, try any other DCs in the Site, then try other DCs in other Sites.

I have ABRT crashes and cores / backtraces from GDB.
Comment 1 Jakub Hrozek 2016-01-19 12:08:46 EST
 * master: 8bd9ec3a8885b01a34863d22aa784e221fc422fb
 * sssd-1-13: b32ea7b1f91b4194e05a1a965310691075ecba23
Comment 2 Mike McCune 2016-03-28 19:16:15 EDT
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions
Comment 4 Dan Lavu 2016-09-19 14:38:01 EDT
Verified against sssd-client-1.14.0-42.el7.x86_64 , though it's sanity *only* since we are testing against MS AD instead of Samba AD. 

Removed A records for NS servers in zone file. 

[root@dell-per230-02 ~]# nslookup bsod2.sssdad2012r2.com

*** Can't find bsod2.sssdad2012r2.com: No answer

[root@dell-per230-02 ~]# rm -rf /var/lib/sss/db/* 
[root@dell-per230-02 ~]# service sssd restart

[root@dell-per230-02 ~]# id Administrator@sssdad2012r2.com
uid=1196000500(administrator@sssdad2012r2.com) gid=1196000513(domain users@sssdad2012r2.com) groups=1196000513(domain users@sssdad2012r2.com),1196000519(enterprise admins@sssdad2012r2.com),1196000518(schema admins@sssdad2012r2.com),1196000512(domain admins@sssdad2012r2.com),1196000520(group policy creator owners@sssdad2012r2.com),1196000572(denied rodc password replication group@sssdad2012r2.com)

Ran for a few hours and SSSD did not crash.
Comment 6 errata-xmlrpc 2016-11-04 03:14:12 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.