From owner-freebsd-stable@FreeBSD.ORG Thu Oct 18 19:33:22 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5BD3016A420 for ; Thu, 18 Oct 2007 19:33:22 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 510F313C46B for ; Thu, 18 Oct 2007 19:33:22 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 3DA1E1CC05F; Thu, 18 Oct 2007 12:33:22 -0700 (PDT) Date: Thu, 18 Oct 2007 12:33:22 -0700 From: Jeremy Chadwick To: freebsd-stable@freebsd.org Message-ID: <20071018193322.GA23372@eos.sc1.parodius.com> Mail-Followup-To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.16 (2007-06-09) Subject: BIND 9.3.4 assertion failure on restart X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Oct 2007 19:33:22 -0000 The following is a reproducible problem on a couple of our DNS servers: (one running 6.2-STABLE, one running 7.0-PRERELEASE): pid 52308 (named), uid 53: exited on signal 6 Oct 18 12:10:21 anubis named[52308]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/task.c:1238: INSIST((((manager->tasks).head == ((void *)0)) ? isc_boolean_true : isc_boolean_false)) failed Oct 18 12:10:21 anubis named[52308]: exiting (due to assertion failure) The problem only occurs when using "/etc/rc.d/named restart". Doing a manual "/etc/rc.d/named stop" then "/etc/rc.d/named start" does not induce the problem. There was one random Internet user who posted about the same issue: http://forums.devshed.com/dns-36/weird-loggs-470845.html There's nothing bizarre about our BIND configuration on these boxes. I've re-written it (by hand) a couple times hoping it might be some syntax problem or other oddity, but it doesn't appear to be. We're not chrooting, and there's no jails. Only thing "non-standard" in rc.conf that's named-related is named_flags="-4". Both boxes exhibiting this problem are running on identical hardware (C2Ds, same memory amount, etc.), with an SMP kernel. The 7.0 box uses the ULE scheduler, while the 6.2 box uses the 4BSD scheduler. I mention this because the master server (running 6.2-STABLE on different hardware, non-SMP kernel, single-core P4 CPU) uses CPUTYPE?=prescott and does not have this problem. I haven't tried adding "-n 1" to named_flags to see if this is a BIND worker thread problem. I can't provide access to these boxes, but I can provide the configuration files and zones (there are not many) to those I trust (dougb@ that means you :) ). If a core is needed, I can likely get one without too much trouble. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |