Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 9 Oct 2001 18:02:00 +0300 (EEST)
From:      Adrian Penisoara <ady@warpnet.ro>
To:        freebsd-security@freebsd.org, bind-users@isc.org
Cc:        Aaron Bush <abush@microcenter.com>, Mark.Andrews@nominum.com
Subject:   named 8.2.4-REL on FreeBSD 4.4 abort due to INSIST() trap 
Message-ID:  <Pine.BSF.4.10.10110091735130.91419-100000@ady.warpnet.ro>

next in thread | raw e-mail | index | archive | help
Hi,

[ CC'ed to two persons that I suspect they've been hit by this issue too ]

  In the last two days we had two signal 6 (ABORT) bind crashes which
were triggered by a software assertion:

Oct  8 15:43:40 quark /kernel: Oct  8 15:43:40 quark named[38899]:
/usr/src/usr.sbin/named/../../contrib/bind/bin/named/ns_maint.c:274:
INSIST(zp->z_time == 0 || zp->z_time > tt.tv_sec) failed.
Oct  8 15:43:40 quark /kernel: Oct  8 15:43:40 quark /kernel: pid 38899
(named), uid 53: exited on signal 6
Oct  9 14:44:21 quark /kernel: Oct  9 14:44:21 quark named[42553]:
/usr/src/usr.sbin/named/../../contrib/bind/bin/named/ns_maint.c:274:
INSIST(zp->z_time == 0 || zp->z_time > tt.tv_sec) failed.
Oct  9 14:44:21 quark /kernel: Oct  9 14:44:21 quark /kernel: pid 42553
(named), uid 53: exited on signal 6

 The relevant code from bind/bin/named/ns_maint.c is:

        /*
         * It is essential that we never try to set a timer in the past
         * or for now because doing so could cause an infinite loop.
         */
        INSIST(zp->z_time == 0 || zp->z_time > tt.tv_sec);

        sched_zone_maint(zp);

 Environment:

FreeBSD quark.warpnet.ro 4.4-PRERELEASE FreeBSD 4.4-PRERELEASE #0: Tue Aug
7 18:11:12 EEST 2001     root@quark.warpnet.ro:/usr/obj/usr/src/sys/QUARK
i386

named 8.2.4-REL Tue Aug  7 12:20:09 EEST 2001
root@quark.warpnet.ro:/usr/obj/usr/src/usr.sbin/named

  Has anyone else experience this ? Is there a fix commited into the CVS
tree for this ? Does 8.2.5-REL fix this (BTW, it hasn't been yet committed
to the FreeBSD CVS repository; the bind8 port hasn't been updated either)?

  Please no "update to current -STABLE, maybe it's been fixed" :-) ...
it's a production server and I prefer to check this out before I jump on
the CVSup bandwagon.

 Thank you,
 Ady (@warpnet.ro)
_______________________________________________________________________
| I don't need to test my programs. I have an error-correcting modem. |
|   (Om I. Baud)                                                      |


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10110091735130.91419-100000>