Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/bind-dyndb-ldap/ticket/66
Plugin deadlocks if new zone was found inside refresh_zones_from_ldap() load and
/etc/named.conf contains "connections 1". It affects also named start.
refresh_zones_from_ldap() holds one connection and second connection is requested inside ldapdb_rdatalist_get() during new zone load.
**Stack with deadlock**
{{{
pthread_cond_wait@@GLIBC_2.3.2() at /usr/src/debug/glibc-2.14-394-g8f3b1ff/nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165 0x7fa359abfae5
semaphore_wait() at /home/pspacek/bind-dyndb-ldap/git/src/semaphore.c:87 0x7fa354d4d806
ldap_pool_getconnection() at /home/pspacek/bind-dyndb-ldap/git/src/ldap_helper.c:2,577 0x7fa354d4bc4b
ldapdb_rdatalist_get() at /home/pspacek/bind-dyndb-ldap/git/src/ldap_helper.c:1,471 0x7fa354d48786
findnode() at /home/pspacek/bind-dyndb-ldap/git/src/ldap_driver.c:421 0x7fa354d41783
zone_get_from_db() at /usr/src/debug/bind-9.8.2rc2/lib/dns/zone.c:3,905 0x7fa35b76338e
zone_postload() at /usr/src/debug/bind-9.8.2rc2/lib/dns/zone.c:3,405 0x7fa35b7663cd
zone_load() at /usr/src/debug/bind-9.8.2rc2/lib/dns/zone.c:1,552 0x7fa35b76c3db
ldap_parse_zoneentry() at /home/pspacek/bind-dyndb-ldap/git/src/ldap_helper.c:1,067 0x7fa354d473be
refresh_zones_from_ldap() at /home/pspacek/bind-dyndb-ldap/git/src/ldap_helper.c:1,162 0x7fa354d47797
manager_create_db_instance() at /home/pspacek/bind-dyndb-ldap/git/src/zone_manager.c:183 0x7fa354d4f861
dynamic_driver_init() at /home/pspacek/bind-dyndb-ldap/git/src/ldap_driver.c:1,329 0x7fa354d435a1
dns_dynamic_db_load() at /usr/src/debug/bind-9.8.2rc2/lib/dns/dynamic_db.c:232 0x7fa35b68ed94
configure_dynamic_db() at /usr/src/debug/bind-9.8.2rc2/bin/named/server.c:1,210 0x7fa35be30bf0
configure_view() at /usr/src/debug/bind-9.8.2rc2/bin/named/server.c:2,784 0x7fa35be30bf0
load_configuration() at /usr/src/debug/bind-9.8.2rc2/bin/named/server.c:4,918 0x7fa35be59b9c
run_server() at /usr/src/debug/bind-9.8.2rc2/bin/named/server.c:5,387 0x7fa35be5b4d5
dispatch() at /usr/src/debug/bind-9.8.2rc2/lib/isc/task.c:1,012 0x7fa35a105eb8
run() at /usr/src/debug/bind-9.8.2rc2/lib/isc/task.c:1,157 0x7fa35a105eb8
start_thread() at /usr/src/debug/glibc-2.14-394-g8f3b1ff/nptl/pthread_create.c:309 0x7fa359abbd90
clone() at /usr/src/debug/glibc-2.14-394-g8f3b1ff/sysdeps/unix/sysv/linux/x86_64/clone.S:115 0x7fa358ff6f5d
}}}
Comment 1RHEL Program Management
2012-07-10 08:50:59 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 2RHEL Program Management
2012-07-10 23:06:46 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Set "connections 1" and "psearch no" in /etc/named.conf and then restart named. It should hang or log deadlock errors.
Fixed version should load and work properly.
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