We're seeing this failure as well. We just installed BIND 9.5.0-P1 on
Alpha/Tru64-4.0G (we had previously been running BIND 8). After an hour
and a half, named terminated with the following log entry:

Aug 6 17:35:34 pangea named[1568]: reloading configuration succeeded
Aug 6 17:35:34 pangea named[1568]: any newly configured zones are now loaded
Aug 6 19:07:15 pangea named[1568]: rbtdb.c:1439: REQUIRE(prev > 0) failed
Aug 6 19:07:15 pangea named[1568]: exiting (due to assertion failure)

Here's what named.conf looks like (this is a caching-only name server):

options {
directory "/etc";
dump-file "/etc/cache_dump.db";
statistics-file "/etc/named_stats.txt";
};

logging {
category lame-servers {null; };
category edns-disabled { null; };
};

include "/etc/rndc.key";

zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "named.local";
};

zone "." {
type hint;
file "named.ca";
};

Has a cause or a fix for this been found?

--

Kai Lanz lanz@stanford.edu School of Earth Sciences 650 723-3400