Assertion failure: what to do next?

[Niall O'Reilly]

	For a change, I'm asking this time.

	On one of our servers, named is hitting an assertion failure.
	I'm looking for hints.  More extensive help is of course also welcome.

	During a scheduled restart of named on one of our servers,
	the following is written to the log.

Nov 30 14:57:07 keadeen named[7333]: shutting down: flushing changes
Nov 30 14:57:07 keadeen named[7333]: stopping command channel on  
127.0.0.1#953
Nov 30 14:57:07 keadeen named[7333]: no longer listening on 127.0.0.1#53
Nov 30 14:57:07 keadeen named[7333]: no longer listening on  
137.43.116.39#53
Nov 30 14:57:07 keadeen named[7333]: no longer listening on  
137.43.128.224#53
Nov 30 14:57:07 keadeen named[7333]: no longer listening on  
137.43.128.11#53
Nov 30 14:57:07 keadeen named[7333]: task.c:1234:
	INSIST((((manager->tasks).head == ((void *)0)) ? isc_boolean_true :  
isc_boolean_false)) failed
Nov 30 14:57:07 keadeen named[7333]: exiting (due to assertion failure)

	A subsequent manual restart "just works".

	The following additional information may be useful.

keadeen(noreilly)18: uname -a
Linux keadeen.ucd.ie 2.4.21-27.ELsmp #1 SMP Wed Dec 1 21:59:02 EST  
2004 i686 i686 i386 GNU/Linux
keadeen(noreilly)18: cat /etc/redhat-release
Red Hat Enterprise Linux ES release 3 (Taroon Update 4)
keadeen(noreilly)19: named -v
BIND 9.4.1-P1
keadeen(noreilly)20:

	The system, according to 'top' or the like, has four "CPUs".
	IIUC, it actually has a pair of dual-core processors.

	BIND was built from the ISC tarball using our SOP, as shown below.

./configure --mandir=/usr/local/share/man
make
sudo bin/tests/system/ifconfig.sh up
make test
sudo bin/tests/system/ifconfig.sh down
make -n install
sudo make install

	As I recall, the only exceptions noted during testing were that several
	thread-related tests were bypassed.


	Best regards,

	Niall O'Reilly
	University College Dublin IT Services

	PGP key ID: AE995ED9 (see www.pgp.net)
	Fingerprint: 23DC C6DE 8874 2432 2BE0 3905 7987 E48D AE99 5ED9