From nobody@FreeBSD.org  Fri Sep 14 17:21:24 2001
Return-Path: <nobody@FreeBSD.org>
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id 3B96B37B401
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 14 Sep 2001 17:21:24 -0700 (PDT)
Received: (from nobody@localhost)
	by freefall.freebsd.org (8.11.4/8.11.4) id f8F0LOA36552;
	Fri, 14 Sep 2001 17:21:24 -0700 (PDT)
	(envelope-from nobody)
Message-Id: <200109150021.f8F0LOA36552@freefall.freebsd.org>
Date: Fri, 14 Sep 2001 17:21:24 -0700 (PDT)
From: Ask Bjoern Hansen <ask@develooper.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: named crashes on 4.4-PRERELEASE
X-Send-Pr-Version: www-1.0

>Number:         30580
>Category:       i386
>Synopsis:       named crashes on 4.4-PRERELEASE
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Sep 14 17:30:00 PDT 2001
>Closed-Date:    Sat Jan 5 20:01:37 PST 2002
>Last-Modified:  Sat Jan 05 20:01:45 PST 2002
>Originator:     Ask Bjoern Hansen
>Release:        4.4-RC FreeBSD 4.4-RC
>Organization:
>Environment:
uname -a
FreeBSD miette.develooper.com 4.4-RC FreeBSD 4.4-RC #5: Wed Sep 12 03:15:29 PDT 2001     root@miette.develooper.com:/home/usrobj/usr/src/sys/MIETTE  i386

>Description:
my named crashes every few hours with this,

(gdb) bt
#0  0x28118764 in kill () from /usr/lib/libc.so.4
#1  0x281547b6 in abort () from /usr/lib/libc.so.4
#2  0x807456d in ns_panic (category=18, dump_core=1,
    format=0x80b7e62 "%s:%d: %s(%s)%s%s failed.")
    at /usr/src/usr.sbin/named/../../contrib/bind/bin/named/ns_glue.c:176
#3  0x80745e7 in ns_assertion_failed (
    file=0x80b1da0 "/usr/src/usr.sbin/named/../../contrib/bind/bin/named/ns_main.c", line=552, type=assert_insist, cond=0x80b1f3b "errno == EINTR",
    print_errno=1)
    at /usr/src/usr.sbin/named/../../contrib/bind/bin/named/ns_glue.c:185
#4  0x805fcc3 in main (argc=1, argv=0xbfbffde0, envp=0xbfbffde4)
    at /usr/src/usr.sbin/named/../../contrib/bind/bin/named/ns_main.c:552


It's both running as a (somewhat busy) authoritative server and as a (very very low traffic) resolving server.
>How-To-Repeat:
I start the named and wait a few hours or half a day and I'll have a new core file.  :-)  


>Fix:

>Release-Note:
>Audit-Trail:

From: Kris Kennaway <kris@obsecurity.org>
To: Ask Bjoern Hansen <ask@develooper.com>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: i386/30580: named crashes on 4.4-PRERELEASE
Date: Sat, 15 Sep 2001 02:41:35 -0700

 --5I6of5zJg18YgZEa
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Fri, Sep 14, 2001 at 05:21:24PM -0700, Ask Bjoern Hansen wrote:
 
 > It's both running as a (somewhat busy) authoritative server and as a (ver=
 y very low traffic) resolving server.
 > >How-To-Repeat:
 > I start the named and wait a few hours or half a day and I'll have a new =
 core file.  :-) =20
 
 This is usually due to problems with your system clock.
 
 Kris
 
 --5I6of5zJg18YgZEa
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org
 
 iD8DBQE7oyJPWry0BWjoQKURAnlTAJ9vw2ssvcWzIk+iIHNL/AgibN6hNwCdFIJc
 sol6FHniKY6AzIwekyhSAwE=
 =Trm3
 -----END PGP SIGNATURE-----
 
 --5I6of5zJg18YgZEa--

From: Kris Kennaway <kris@obsecurity.org>
To: Ask Bjoern Hansen <ask@develooper.com>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: i386/30580: named crashes on 4.4-PRERELEASE
Date: Sat, 15 Sep 2001 02:41:35 -0700

 --5I6of5zJg18YgZEa
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Fri, Sep 14, 2001 at 05:21:24PM -0700, Ask Bjoern Hansen wrote:
 
 > It's both running as a (somewhat busy) authoritative server and as a (ver=
 y very low traffic) resolving server.
 > >How-To-Repeat:
 > I start the named and wait a few hours or half a day and I'll have a new =
 core file.  :-) =20
 
 This is usually due to problems with your system clock.
 
 Kris
 
 --5I6of5zJg18YgZEa
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org
 
 iD8DBQE7oyJPWry0BWjoQKURAnlTAJ9vw2ssvcWzIk+iIHNL/AgibN6hNwCdFIJc
 sol6FHniKY6AzIwekyhSAwE=
 =Trm3
 -----END PGP SIGNATURE-----
 
 --5I6of5zJg18YgZEa--

From: Kris Kennaway <kris@obsecurity.org>
To: Ask Bjoern Hansen <ask@develooper.com>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: i386/30580: named crashes on 4.4-PRERELEASE
Date: Sat, 15 Sep 2001 02:41:35 -0700

 --5I6of5zJg18YgZEa
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Fri, Sep 14, 2001 at 05:21:24PM -0700, Ask Bjoern Hansen wrote:
 
 > It's both running as a (somewhat busy) authoritative server and as a (ver=
 y very low traffic) resolving server.
 > >How-To-Repeat:
 > I start the named and wait a few hours or half a day and I'll have a new =
 core file.  :-) =20
 
 This is usually due to problems with your system clock.
 
 Kris
 
 --5I6of5zJg18YgZEa
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org
 
 iD8DBQE7oyJPWry0BWjoQKURAnlTAJ9vw2ssvcWzIk+iIHNL/AgibN6hNwCdFIJc
 sol6FHniKY6AzIwekyhSAwE=
 =Trm3
 -----END PGP SIGNATURE-----
 
 --5I6of5zJg18YgZEa--

From: Ask Bjoern Hansen <ask@develooper.com>
To: Kris Kennaway <kris@obsecurity.org>, <dima@freebsd.org>
Cc: <freebsd-gnats-submit@FreeBSD.org>
Subject: Re: i386/30580: named crashes on 4.4-PRERELEASE
Date: Sat, 15 Sep 2001 05:32:17 -0700 (PDT)

 On Sat, 15 Sep 2001, Kris Kennaway wrote:
 
 > On Fri, Sep 14, 2001 at 05:21:24PM -0700, Ask Bjoern Hansen wrote:
 >
 > > It's both running as a (somewhat busy) authoritative server and as a (very very low traffic) resolving server.
 > > >How-To-Repeat:
 > > I start the named and wait a few hours or half a day and I'll have a new core file.  :-)
 >
 > This is usually due to problems with your system clock.
 
 As in the clock keeping track of the time of day? That sounds really
 odd.  I searched the mail archives for more references about this,
 but didn't find anything.  Can you point me in the right direction?
 
 I've recently had problems with the IDE (don't ask) drive and
 haven't had time to replace it yet; could that be related?
 
 
  - ask
 
 -- 
 ask bjoern hansen, http://ask.netcetera.dk/   !try; do();
 
 

From: Kris Kennaway <kris@obsecurity.org>
To: Ask Bjoern Hansen <ask@develooper.com>
Cc: Kris Kennaway <kris@obsecurity.org>, dima@freebsd.org,
	freebsd-gnats-submit@freebsd.org
Subject: Re: i386/30580: named crashes on 4.4-PRERELEASE
Date: Sat, 15 Sep 2001 13:43:41 -0700

 --7AUc2qLy4jB3hD7Z
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Sat, Sep 15, 2001 at 05:32:17AM -0700, Ask Bjoern Hansen wrote:
 > On Sat, 15 Sep 2001, Kris Kennaway wrote:
 >=20
 > > On Fri, Sep 14, 2001 at 05:21:24PM -0700, Ask Bjoern Hansen wrote:
 > >
 > > > It's both running as a (somewhat busy) authoritative server and as a =
 (very very low traffic) resolving server.
 > > > >How-To-Repeat:
 > > > I start the named and wait a few hours or half a day and I'll have a =
 new core file.  :-)
 > >
 > > This is usually due to problems with your system clock.
 >=20
 > As in the clock keeping track of the time of day? That sounds really
 > odd.  I searched the mail archives for more references about this,
 > but didn't find anything.  Can you point me in the right direction?
 
 Search the -security mailing list for "named assertion failed".  Since
 you didn't post the actual error message it's hard to verify it's the
 same thing.
 
 > I've recently had problems with the IDE (don't ask) drive and
 > haven't had time to replace it yet; could that be related?
 
 I haven't heard of that, but it's not impossible.
 
 Kris
 --7AUc2qLy4jB3hD7Z
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org
 
 iD8DBQE7o718Wry0BWjoQKURAohlAJ9oOo6bC/9GjZWg5fGHoD/ykVDq+QCgh+jK
 8axTRzzysRBc1+cmEjXVvBE=
 =jZFn
 -----END PGP SIGNATURE-----
 
 --7AUc2qLy4jB3hD7Z--

From: Kris Kennaway <kris@obsecurity.org>
To: Ask Bjoern Hansen <ask@develooper.com>,
	freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: i386/30580: named crashes on 4.4-PRERELEASE
Date: Sun, 23 Sep 2001 16:49:10 -0700

 On Sat, Sep 15, 2001 at 01:50:02PM -0700, Kris Kennaway wrote:
 
 >  On Sat, Sep 15, 2001 at 05:32:17AM -0700, Ask Bjoern Hansen wrote:
 >  > On Sat, 15 Sep 2001, Kris Kennaway wrote:
 >  >=20
 >  > > On Fri, Sep 14, 2001 at 05:21:24PM -0700, Ask Bjoern Hansen wrote:
 >  > >
 >  > > > It's both running as a (somewhat busy) authoritative server and as a =
 >  (very very low traffic) resolving server.
 >  > > > >How-To-Repeat:
 >  > > > I start the named and wait a few hours or half a day and I'll have a =
 >  new core file.  :-)
 >  > >
 >  > > This is usually due to problems with your system clock.
 >  >=20
 >  > As in the clock keeping track of the time of day? That sounds really
 >  > odd.  I searched the mail archives for more references about this,
 >  > but didn't find anything.  Can you point me in the right direction?
 >  
 >  Search the -security mailing list for "named assertion failed".  Since
 >  you didn't post the actual error message it's hard to verify it's the
 >  same thing.
 >  
 >  > I've recently had problems with the IDE (don't ask) drive and
 >  > haven't had time to replace it yet; could that be related?
 >  
 >  I haven't heard of that, but it's not impossible.
 
 Did you follow this up yet?
 
 Kris

From: Ask Bjoern Hansen <ask@develooper.com>
To: Kris Kennaway <kris@obsecurity.org>
Cc: <freebsd-gnats-submit@FreeBSD.org>, Dima Ruban <dima@rdy.com>
Subject: Re: i386/30580: named crashes on 4.4-PRERELEASE
Date: Mon, 24 Sep 2001 03:56:14 -0700 (PDT)

 On Sun, 23 Sep 2001, Kris Kennaway wrote:
 
 > >  >=20
 > >  > > On Fri, Sep 14, 2001 at 05:21:24PM -0700, Ask Bjoern Hansen wrote:
 > >  > >
 > >  > > > It's both running as a (somewhat busy) authoritative server and as a =
 > >  (very very low traffic) resolving server.
 > >  > > > >How-To-Repeat:
 > >  > > > I start the named and wait a few hours or half a day and I'll have a =
 > >  new core file.  :-)
 > >  > >
 > >  > > This is usually due to problems with your system clock.
 > >  >=20
 > >  > As in the clock keeping track of the time of day? That sounds really
 > >  > odd.  I searched the mail archives for more references about this,
 > >  > but didn't find anything.  Can you point me in the right direction?
 > >
 > >  Search the -security mailing list for "named assertion failed".  Since
 > >  you didn't post the actual error message it's hard to verify it's the
 > >  same thing.
 > >
 > >  > I've recently had problems with the IDE (don't ask) drive and
 > >  > haven't had time to replace it yet; could that be related?
 > >
 > >  I haven't heard of that, but it's not impossible.
 >
 > Did you follow this up yet?
 
 no; I was actually just going to do so to tell that it seems
 resolved.  I replaced the faulty drive and it had not crashed since
 (and actually it took a break in the last few days before I replaced
 it).
 
 Anyway, it crashed again:
 
 (gdb) bt
 #0  0x28118764 in kill () from /usr/lib/libc.so.4
 #1  0x281547b6 in abort () from /usr/lib/libc.so.4
 #2  0x807456d in ns_panic (category=18, dump_core=1,
     format=0x80b7e62 "%s:%d: %s(%s)%s%s failed.")
     at /usr/src/usr.sbin/named/../../contrib/bind/bin/named/ns_glue.c:176
 #3  0x80745e7 in ns_assertion_failed (
     file=0x80b1da0 "/usr/src/usr.sbin/named/../../contrib/bind/bin/named/ns_main.c", line=552, type=assert_insist, cond=0x80b1f3b "errno == EINTR",
     print_errno=1)
     at /usr/src/usr.sbin/named/../../contrib/bind/bin/named/ns_glue.c:185
 #4  0x805fcc3 in main (argc=1, argv=0xbfbffde0, envp=0xbfbffde4)
     at /usr/src/usr.sbin/named/../../contrib/bind/bin/named/ns_main.c:552
 
 
 from syslog:
 
 Sep 23 06:59:12 miette named[201]: /usr/src/usr.sbin/named/../../contrib/bind/bin/named/ns_main. c:552: INSIST(errno == EINTR): Invalid argument failed.
 Sep 23 06:59:12 miette named[201]: /usr/src/usr.sbin/named/../../contrib/bind/bin/named/ns_main. c:552: INSIST(errno == EINTR): Invalid argument failed.
 Sep 23 06:59:14 miette /kernel: pid 201 (named), uid 0: exited on signal 6 (core dumped)
 
 There are no other messages around the same time. No funny hardware
 issues and the box is using NTP and I haven't seen any messages from
 ntpd about funny things going on with the time on the box. (Which was
 what the archived messages about the named assertion failure
 indicated).  :-/
 
 Any clues would be most appreciated.
 
 
  - ask
 
 -- 
 ask bjoern hansen, http://ask.netcetera.dk/   !try; do();
 
 

From: Kris Kennaway <kris@obsecurity.org>
To: Ask Bjoern Hansen <ask@develooper.com>
Cc: Kris Kennaway <kris@obsecurity.org>,
	freebsd-gnats-submit@FreeBSD.org, Dima Ruban <dima@rdy.com>
Subject: Re: i386/30580: named crashes on 4.4-PRERELEASE
Date: Mon, 24 Sep 2001 04:54:11 -0700

 --BXVAT5kNtrzKuDFl
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Mon, Sep 24, 2001 at 03:56:14AM -0700, Ask Bjoern Hansen wrote:
 
 > from syslog:
 >=20
 > Sep 23 06:59:12 miette named[201]: /usr/src/usr.sbin/named/../../contrib/=
 bind/bin/named/ns_main. c:552: INSIST(errno =3D=3D EINTR): Invalid argument=
  failed.
 > Sep 23 06:59:12 miette named[201]: /usr/src/usr.sbin/named/../../contrib/=
 bind/bin/named/ns_main. c:552: INSIST(errno =3D=3D EINTR): Invalid argument=
  failed.
 > Sep 23 06:59:14 miette /kernel: pid 201 (named), uid 0: exited on signal =
 6 (core dumped)
 >=20
 > There are no other messages around the same time. No funny hardware
 > issues and the box is using NTP and I haven't seen any messages from
 > ntpd about funny things going on with the time on the box. (Which was
 > what the archived messages about the named assertion failure
 > indicated).  :-/
 >=20
 > Any clues would be most appreciated.
 
 You probably should take this up on the BIND support list.
 
 Kris
 
 --BXVAT5kNtrzKuDFl
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org
 
 iD8DBQE7rx7jWry0BWjoQKURApiHAJ9M9cB5zCNS7G6QiZjgFNKLwSltBwCg8rLO
 rJgGtbC7LYNIhOtFAldLCfg=
 =SuzO
 -----END PGP SIGNATURE-----
 
 --BXVAT5kNtrzKuDFl--
State-Changed-From-To: open->feedback 
State-Changed-By: asmodai 
State-Changed-When: Thu Nov 15 09:25:13 PST 2001 
State-Changed-Why:  
Did you try the BIND in the latest STABLE? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=30580 
State-Changed-From-To: feedback->closed 
State-Changed-By: kris 
State-Changed-When: Sat Jan 5 20:01:37 PST 2002 
State-Changed-Why:  
Feedback timeout 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=30580 
>Unformatted:
