From owner-freebsd-questions Tue Dec 24 13: 6:57 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 619AD37B401 for ; Tue, 24 Dec 2002 13:06:55 -0800 (PST) Received: from nemesis.systems.pipex.net (nemesis.systems.pipex.net [62.241.160.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD15643E4A for ; Tue, 24 Dec 2002 13:06:54 -0800 (PST) (envelope-from stacey@vickiandstacey.com) Received: from [192.168.1.8] (81-86-129-77.dsl.pipex.com [81.86.129.77]) by nemesis.systems.pipex.net (Postfix) with ESMTP id 37D6416007F8F; Tue, 24 Dec 2002 21:06:38 +0000 (GMT) Subject: Re: what do these named messages mean? and ideas? From: Stacey Roberts Reply-To: stacey@vickiandstacey.com To: Gary D Kline Cc: FreeBSD Mailing List In-Reply-To: <20021224205738.GA83356@tao.thought.org> References: <20021224205738.GA83356@tao.thought.org> Content-Type: text/plain Organization: Message-Id: <1040764005.58381.219.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 24 Dec 2002 21:06:46 +0000 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 2002-12-24 at 20:57, Gary D Kline wrote: > Hi People, > > I've switched back to ipf/ipf.rules until I can figure out > how to get dhcp working with ipfw. Does anyone have any > idea why the following messages are being output to > /var/log/messages? --These messages may not be a concern > since named really *is* running. > > This looks like a packet-filter issue and I am stumped? > > Anybody?? > > thanks in advance for and insights, > > gary > > > > > (date) sage /usr/local/sbin/named[722]: starting BIND 9.1.3 -c /etc/namedb/named.conf > (date) sage /usr/local/sbin/named[722]: could not listen on UDP socket: address in use > (date) sage /usr/local/sbin/named[722]: creating IPv4 interface dc0 failed; interface ignored > (date) sage /usr/local/sbin/named[722]: could not listen on UDP socket: address in use > (date) sage /usr/local/sbin/named[722]: creating IPv4 interface dc1 failed; interface ignored > (date) sage /usr/local/sbin/named[722]: could not listen on UDP socket: address in use > (date) sage /usr/local/sbin/named[722]: creating IPv4 interface lo0 failed; interface ignored > (date) sage /usr/local/sbin/named[722]: not listening on any interfaces > (date) sage /usr/local/sbin/named[722]: could not get query source dispatcher > (date) sage /usr/local/sbin/named[722]: loading configuration: address in use > (date) sage /usr/local/sbin/named[722]: exiting (due to fatal error) I don't use IPF here, I'm not sure that the above messages are indeed anything to do with the packet filter. *Which* named is running? - sockstat -4l | grep -i named If anything, I'd try investigating what *is* using (presumably 53) the address space requried by bind. If it proves to be some "other" named process, I'd try stopping and restarting bind. Regards, Stacey -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message