Red Hat Bugzilla – Bug 1292458
sssd_be AD segfaults on missing A record
Last modified: 2016-05-10 16:25:53 EDT
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: 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: 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.
* master: 8bd9ec3a8885b01a34863d22aa784e221fc422fb
* sssd-1-13: b32ea7b1f91b4194e05a1a965310691075ecba23
Verified sanity only, against sssd-client-1.13.3-19.el6.x86_64, SSSD did not crash.
[root@sssdqe5 ~]# id firstname.lastname@example.org
uid=129100790(email@example.com) gid=1606600583(domain firstname.lastname@example.org) groups=1606600583(domain email@example.com),139544400(group policy creator firstname.lastname@example.org),1606600582(domain email@example.com),1606600588(schema firstname.lastname@example.org),1425621082(denied rodc password replication email@example.com),1606600589(enterprise firstname.lastname@example.org)
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.