bind-dyndb-ldap

Clone

#142 BIND is crashed due to race condition during forwarder reconfiguration
Closed: Fixed None Opened 9 years ago by pspacek.

Closed: Fixed
Reopen Issue

It seems that forwarder reconfiguration needs better locking than we have now. Our ability to properly fix this problem depends on [1158763 in BIND]]([https://bugzilla.redhat.com/show_bug.cgi?id=1158763|bug).

Details including reproducer follow:

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1126841

Description of problem:
named is crashed at the time finding nodes in rbt because it is already freed
in some other thread.

Version-Release number of selected component (if applicable):
bind-9.8.2-0.17.rc1.el6_4.6.x86_64
bind-dyndb-ldap-2.3-5.el6.x86_64
bind-libs-9.8.2-0.17.rc1.el6_4.6.x86_64
bind-utils-9.8.2-0.17.rc1.el6_4.6.x86_64

RHEL 6.5

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
named is crashed

Expected results:
named should not crashed.

Additional info:

Results of planning meeting held on 2014-11-04.

attachment
update_server.py

attachment
query.py

Reproducer

Taken from https://bugzilla.redhat.com/show_bug.cgi?id=1126841#c14:

  1. install ipa-server, bind-dyndb-ldap, bind
  2. run $ ipa-server-install --setup-dns
  3. stop named
  4. start named - $ named -u named -fg -n 20
  5. run in different terminals both attached scripts
  6. wait for named to crash :)

Metadata Update from @pspacek:
- Issue assigned to pspacek
- Issue set to the milestone: Fedora 22
7 years ago

Login to comment on this ticket.

Metadata
None
None
None
critical
https://bugzilla.redhat.com/show_bug.cgi?id=1126841
None
None
274a3b1cd0ed58f307f4a8d0a7c2f4006fb5e35e
None
None
defect
ldap driver
2.3
nihsyndrome, crash
None
Powered by Pagure 5.13.3
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.