From owner-freebsd-security  Mon Mar 26  8:30:33 2001
Delivered-To: freebsd-security@freebsd.org
Received: from coloradosurf.com (c1520339-a.lakwod1.co.home.com [24.179.159.58])
	by hub.freebsd.org (Postfix) with ESMTP id B8FAA37B719
	for <security@freebsd.org>; Mon, 26 Mar 2001 08:30:12 -0800 (PST)
	(envelope-from mike@coloradosurf.com)
Received: (from mike@localhost)
	by coloradosurf.com (8.9.3/8.9.3) id JAA08654
	for security@freebsd.org; Mon, 26 Mar 2001 09:24:46 -0700 (MST)
	(envelope-from mike)
Date: Mon, 26 Mar 2001 09:24:46 -0700
From: mike <mike@coloradosurf.com>
To: security@freebsd.org
Subject: named dying on INSIST
Message-ID: <20010326092446.A8530@coloradosurf.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I humbly ask the great minds . . .

Has anyone seen this or can lend insight?

Over the weekend, my named (primary nameserver) died unexpectedly.

Mar 24 02:04:53 ns1 named[6470]:
/usr/src/lib/libbind/../../contrib/bind/lib/isc/ev_timers.c:114:
INSIST(now.tv_usec >= 0 && now.tv_usec < 1000000) failed.
Mar 24 02:04:53 ns1 named[6470]:
/usr/src/lib/libbind/../../contrib/bind/lib/isc/ev_timers.c:114:
INSIST(now.tv_usec >= 0 && now.tv_usec < 1000000) failed.
Mar 24 02:04:54 ns1 /kernel: pid 6470 (named), uid 53: exited on signal
6


root@ns1#named -v
named 8.2.3-REL Sat Feb  3 21:11:38 MST 2001

The apparent problem (or more likely the alarm?)
from /usr/src/contrib/bind/lib/isc/ev_timers.c
struct timespec
evNowTime() {
        struct timeval now;

        if (gettimeofday(&now, NULL) < 0)
                return (evConsTime(0, 0));
        INSIST(now.tv_usec >= 0 && now.tv_usec < 1000000);
        return (evTimeSpec(now));
}

clue --> less


TIA,

mike

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message