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.
Description of problem:
named will crash semi-randomly (twice in 3 weeks) with a assertion failure.
named[19833]: 14-Jul-2012 12:18:28.122 general:
critical: rbtdb.c:1619: INSIST(!((void *)((node)->deadlink.prev) !=
(void *)(-1))) failed
named[19833]: 14-Jul-2012 12:18:28.131 general:
critical: exiting (due to assertion failure)
Abrtd captures it and here is the stack trace,
#0 0x00007f22d57af8a5 in raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x00007f22d57b1085 in abort () at abort.c:92
#2 0x00007f22d7f76e14 in assertion_failed (file=<value optimized out>,
line=<value optimized out>, type=<value optimized out>, cond=<value
optimized out>) at ./main.c:219
#3 0x00007f22d692d89a in isc_assertion_failed (file=<value optimized
out>, line=<value optimized out>, type=<value optimized out>,
cond=<value optimized out>) at assertions.c:57
#4 0x00007f22d78074a2 in cleanup_dead_nodes (rbtdb=0x7f22d0609010,
bucketnum=<value optimized out>) at rbtdb.c:1600
#5 0x00007f22d7807726 in reactivate_node (rbtdb=0x7f22d0609010,
node=0x7f22c075cb68, treelocktype=isc_rwlocktype_write) at rbtdb.c:1662
#6 0x00007f22d78092cb in findnodeintree (rbtdb=0x7f22d0609010,
tree=0x7f22d060d010, name=0x7f22c3621920, create=isc_boolean_true,
nodep=0x7f22d3a10c70) at rbtdb.c:2573
#7 0x00007f22d786929f in cache_name (fctx=0x7f22c363d438,
name=0x7f22c3621920, addrinfo=0x7f22c092b430, now=1340718604) at
resolver.c:4427
#8 0x00007f22d786f4c0 in cache_message (task=0x7f22d065f380,
event=<value optimized out>) at resolver.c:4740
#9 resquery_response (task=0x7f22d065f380, event=<value optimized out>)
at resolver.c:7125
#10 0x00007f22d694c2f8 in dispatch (uap=0x7f22d7ee7010) at task.c:1012
#11 run (uap=0x7f22d7ee7010) at task.c:1157
#12 0x00007f22d6301851 in start_thread (arg=0x7f22d3a12700) at
pthread_create.c:301
#13 0x00007f22d586467d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115
This crash seems to be fixed upstream,
https://lists.isc.org/pipermail/bind-users/2012-July/088082.html
Version-Release number of selected component (if applicable):
bind-9.8.2-0.10.rc1.el6.x86_64
How reproducible:
Unclear how to reproduce it manually as we have not been able to capture the state of the daemon around when it dies.
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info: