Red Hat Bugzilla – Bug 829353
bind-dyndb-ldap crashes when NS is not resolvable
Last modified: 2015-05-20 11:51:33 EDT
+++ This bug was initially created as a clone of Bug #827401 +++ Description of problem: bind-dyndb-ldap crashes during freeipa unit tests (psearch enabled). The root cause is probably an unresolvable NS record zone root record. Backtrace: (gdb) bt #0 0x00007ffff50a0965 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x00007ffff50a2118 in __GI_abort () at abort.c:91 #2 0x000055555558527b in assertion_failed (file=<optimized out>, line=<optimized out>, type=<optimized out>, cond=<optimized out>) at ./main.c:219 #3 0x00007ffff62bec3a in isc_assertion_failed (file=file@entry=0x7ffff799c47b "zone.c", line=<optimized out>, type=type@entry=isc_assertiontype_require, cond=cond@entry=0x7ffff799c677 "zone->db != ((void *)0)") at assertions.c:57 #4 0x00007ffff79453d7 in zone_detachdb (zone=<optimized out>) at zone.c:12935 #5 zone_detachdb (zone=0x7fffec5bbff0) at zone.c:12934 #6 0x00007ffff7945445 in zone_unload (zone=zone@entry=0x7fffec5bbff0) at zone.c:9105 #7 0x00007ffff7949664 in dns_zone_unload (zone=0x7fffec5bbff0) at zone.c:9045 #8 0x00007ffff249ca8e in ldap_delete_zone2 (inst=inst@entry=0x7ffff7fc9f10, name=name@entry=0x7ffff3ff2d10, lock=lock@entry=isc_boolean_true) at ldap_helper.c:787 #9 0x00007ffff249e414 in ldap_delete_zone (dn=<optimized out>, inst=0x7ffff7fc9f10, lock=<optimized out>) at ldap_helper.c:812 #10 update_action (task=<optimized out>, event=0x7ffff26f6a60) at ldap_helper.c:2749 #11 0x00007ffff62de13e in dispatch (manager=0x7ffff7fa8010) at task.c:1109 #12 run (uap=0x7ffff7fa8010) at task.c:1279 #13 0x00007ffff5c93d14 in start_thread (arg=0x7ffff3ff3700) at pthread_create.c:309 #14 0x00007ffff515c99d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Zone LDIF is attached. Version-Release number of selected component (if applicable): bind-dyndb-ldap-1.1.0-0.10.b2.fc17.x86_64 How reproducible: Steps to Reproduce: 1. Use attached LDIF to create a zone 2. Run named 3. Actual results: bind-dyndb-ldap crashes with zone with this LDIF Expected results: bind-dyndb-ldap does not crash Additional info: --- Additional comment from mkosek@redhat.com on 2012-06-01 07:18:27 EDT --- Created attachment 588407 [details] /etc/named.conf --- Additional comment from mkosek@redhat.com on 2012-06-01 07:20:27 EDT --- Created attachment 588408 [details] Zones --- Additional comment from pspacek@redhat.com on 2012-06-05 11:31:18 EDT --- I can't reproduce it with given LDIF. Please provide exact BIND version and your /etc/named.conf. --- Additional comment from mkosek@redhat.com on 2012-06-05 11:39:46 EDT --- I attached /etc/named.conf to this ticket. I can always reproduce this issue when running FreeIPA DNS unit tests and have psearch enabled. bind version: bind-9.9.1-2.P1.fc17.x86_64 --- Additional comment from pspacek@redhat.com on 2012-06-06 09:50:55 EDT --- Upstream ticket: https://fedorahosted.org/bind-dyndb-ldap/ticket/77
Fixed in upstream: http://git.fedorahosted.org/git/?p=bind-dyndb-ldap.git;a=commit;h=0dccccec9cede75bd254f723bc9a49592c24a44b
*** Bug 821958 has been marked as a duplicate of this bug. ***
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. http://rhn.redhat.com/errata/RHBA-2013-0359.html