Date: Mon, 28 Jun 1999 17:05:36 -0700 From: Gary Schrock <root@eyelab.psy.msu.edu> To: freebsd-stable@freebsd.org Subject: named dies after being up for a little while in 3.2-stable? Message-ID: <4.2.0.58.19990628165456.00abe6f0@localhost>
next in thread | raw e-mail | index | archive | help
I just updated a box from somewhere in the 3.1-stable area to about last
friday's (6/26/99) 3.2-stable line, and since doing this named seems to be
keeling over dead after being up for a little while (suspiciously, the
first time it was exactly 1 hour, it also seems to have occured exactly 15
minutes after bringing it back up). The relevant log in messages is:
Jun 28 16:07:44 eyelab named[122]:
/usr/src/lib/libbind/../../contrib/bind/lib/isc/memcluster.c:246:
INSIST(stats[size].gets != 0) failed.
Below is the contents of my named.conf file:
options {
directory "/etc/namedb";
forwarders {
35.8.2.41;
};
dump-file "s/named_dump.db";
};
zone "." {
type hint;
file "named.root";
};
zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "localhost.rev";
};
zone "msu.edu" {
type slave;
file "s/msu.zone.bak";
masters {
35.8.2.41;
};
};
zone "8.35.in-addr.arpa" {
type slave;
file "s/msu.rev.bak";
masters {
35.8.2.41;
};
};
Anybody have any suggestions?
Thanks,
Gary Schrock
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.2.0.58.19990628165456.00abe6f0>