Sanity Check - BIND 9.4.1 assert failure

Dan Mahoney, System Admin danm at prime.gushi.org
Tue Aug 21 03:18:47 EDT 2007


Hey all,

My primary resolver keeps dying on me on signal six -- with the following 
error:

Aug 18 03:38:26 <daemon.crit> prime named[72049]: validator.c:202: 
INSIST(val->event == ((void *)0)) failed
Aug 18 03:38:26 <console.info> prime kernel: Aug 18 03:38:26 <daemon.crit> 
prime named[72049]: validator.c:202: INSIST(val->event ==
  ((void *)0)) failed
Aug 18 03:38:26 <daemon.crit> prime named[72049]: exiting (due to 
assertion failure)
Aug 18 03:38:26 <console.info> prime kernel: Aug 18 03:38:26 <daemon.crit> 
prime named[72049]: exiting (due to assertion failure)
Aug 18 03:38:26 <kern.info> prime kernel: pid 72049 (named), uid 53: 
exited on signal 6

I'm about to post to comp.protocols.dns.bind -- but I wanted to ask if 
anyone else here has seen anything similar, since this appears to be 
related to DNSSEC.

-Dan Mahoney

--

"Don't think of it as beer, think of it as a flavored motor oil."

-Jeremiah Kristal, on Guinness
3/29/05, 9:52 AM

--------Dan Mahoney--------
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144   AIM: LarpGM
Site:  http://www.gushi.org
---------------------------




More information about the Dnssec-deployment mailing list