misc/135017: BIND. exiting (due to assertion failure).
resolver.c:1108 failed
Alexey Kostyuk
unitoff at gmail.com
Thu May 28 05:40:01 UTC 2009
>Number: 135017
>Category: misc
>Synopsis: BIND. exiting (due to assertion failure). resolver.c:1108 failed
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu May 28 05:40:00 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator: Alexey Kostyuk
>Release: 6.3-RELEASE-p9
>Organization:
JS Centertelecom
>Environment:
FreeBSD persey.kaluga.ru 6.3-RELEASE-p9 FreeBSD 6.3-RELEASE-p9 #12: Thu Jan 22 11:36:23 MSK 2009 unit at persey.kaluga.ru:/usr/obj/usr/src/sys/PERSEY i386
>Description:
I use native bind in freebsd 6.3 (include all freebsd patches and updates). Number of zones in my configurations - 525. Maximum recursive clients 1000, connection via tcp - 100. I allow recursive queries only for my networks. All worked fine for a long time, but recently bind died with an error in my /var/log/messages:
May 25 15:24:59 persey kernel: pid 27591 (named), uid 53: exited on signal 6
and errors in /var/named/var/log/named.log:
27-May-2009 22:51:27.672 critical: /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/resolver.c:1108: INSIST(query->dispatch != ((void *)0)) failed
27-May-2009 22:51:27.672 critical: exiting (due to assertion failure)
The problem was repeated 2 times and I could not find the cause of this error.
Maybe somebody can help me
My rndc status:
persey# rndc status
number of zones: 525
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 232/1000
tcp clients: 0/100
server is up and running
My bind version
persey# named -v
BIND 9.3.4-P1
>How-To-Repeat:
I could not find the cause of this error
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list