From owner-freebsd-stable Mon Jun 28 13:59:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from eyelab.psy.msu.edu (eyelab.psy.msu.edu [35.8.64.179]) by hub.freebsd.org (Postfix) with ESMTP id 09E74151DD for ; Mon, 28 Jun 1999 13:59:13 -0700 (PDT) (envelope-from root@eyelab.psy.msu.edu) Received: from DEVEL-EYELAB (eyelab.psy.msu.edu [35.8.64.179]) by eyelab.psy.msu.edu (8.9.3/8.9.2) with ESMTP id QAA00792 for ; Mon, 28 Jun 1999 16:59:11 -0400 (EDT) (envelope-from root@eyelab.psy.msu.edu) Message-Id: <4.2.0.58.19990628165456.00abe6f0@localhost> X-Sender: root@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 28 Jun 1999 17:05:36 -0700 To: freebsd-stable@freebsd.org From: Gary Schrock Subject: named dies after being up for a little while in 3.2-stable? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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