Subject: bin/34269: named crash
To: None <firstname.lastname@example.org, email@example.com>
From: None <firstname.lastname@example.org>
Date: 08/23/2006 22:00:00
>Synopsis: /home/builds/ab/netbsd-3-0-1-RELEASE/src/dist/bind/lib/dns/name.c:823: REQUIRE(first <= source->labels) failed
>Arrival-Date: Wed Aug 23 22:00:00 +0000 2006
>Originator: Edgar Fuß
>Release: NetBSD 3.0.1
System: NetBSD orion.intra.net 3.0.1 NetBSD 3.0.1 (GENERIC) #0: Fri Jul 14 04:01:19 UTC 2006 email@example.com:/home/builds/ab/netbsd-3-0-1-RELEASE/sparc/200607131826Z-obj/home/builds/ab/netbsd-3-0-1-RELEASE/src/sys/arch/sparc/compile/GENERIC sparc
Since simultaneously both updating from 2.1 to 3.0.1 and turning my forward-only ns to one handling a local zone, I observe frequent crashes of named. Mostly, the backtrace stops after one frame (the topmost often being dns_name_copy or vnsprintf), but today I got a complete one and even an Assertion Failure in the log: /home/builds/ab/netbsd-3-0-1-RELEASE/src/dist/bind/lib/dns/name.c:823: REQUIRE(first <= source->labels) failed.
Any idea how to track down the problem?
The issue may be related to reloading the config in ppp's ip-up and ip-down scripts or one of the network interfaces going up/down due to powering the attached switch on/off.
Not known precisely.