From owner-freebsd-stable@FreeBSD.ORG Tue Nov 16 22:32:39 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CD0116A4CE for ; Tue, 16 Nov 2004 22:32:39 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C78E43D3F for ; Tue, 16 Nov 2004 22:32:39 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAGMVBBL060053; Tue, 16 Nov 2004 17:31:11 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAGMVBMe060050; Tue, 16 Nov 2004 22:31:11 GMT (envelope-from robert@fledge.watson.org) Date: Tue, 16 Nov 2004 22:31:11 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Samuel Trommel In-Reply-To: <20041115185155.9080D43D3F@mx1.FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: Named 9.3.0 && weird error at bootup X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 22:32:39 -0000 On Mon, 15 Nov 2004, Samuel Trommel wrote: > Recently I upgraded from 5.2.1-release to 5.3-release. When I try to > start named I get a weird error: > > Nov 15 19:23:12 freebsd named[1152]: starting BIND 9.3.0 -4 -u bind -t > /var/named/etc/namedb/ -c /etc/named.conf > > Nov 15 19:23:12 freebsd named[1152]: command channel listening on > 0.0.0.0#953 > > Nov 15 19:23:12 freebsd named[1152]: > /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/errno2result.c:109 > : unexpected error: > > Nov 15 19:23:12 freebsd named[1152]: unable to convert errno to > isc_result: 6: Device not configured > > After this my named is workin well, but wondering what this could be?? If this is reproduceable, it would be useful to try running named under ktrace and see which system call and arguments resulted in ENXIO. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research