Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 24 Dec 2002 15:32:49 -0600 (CST)
From:      Shane Kinney <shane@freebsdhackers.net>
To:        Gary D Kline <kline@thought.org>
Cc:        FreeBSD Mailing List <freebsd-questions@FreeBSD.ORG>
Subject:   Re: what do these named messages mean? and ideas?
Message-ID:  <20021224152414.X58667-100000@sigma.freebsdhackers.net>
In-Reply-To: <20021224205738.GA83356@tao.thought.org>
References:  <20021224205738.GA83356@tao.thought.org>

next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 24 Dec 2002, Gary D Kline wrote:

> 	These messages may not be a concern
> 	since named really *is* running.
>
> 	This looks like a packet-filter issue and I am stumped?

First things first.  Turn of named.  Then turn off IPF.  Attempt to
start named again, then see if you still see thoes messages showing up
in /var/log/messages.  If you don't then you may have some IPF rule set
issues.  We won't know until you paste them to this list.

> (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)

Looking at this, it seems like BIND attemts to start up, can not listen
on a socket, then dies.  So are you positive that the named process is
running on your server?  Did you accidently try to start another
instantce of named?

Hope this helps points you in the right direction.

~Shane
PGP Key: http://www.freebsdhackers.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE+CNKEtGSLUf7ussURAr0tAJ4hz/JSCmttzXtDobnsHnVsXt2NygCaAreZ
EPpHBm/uCp5s1jf/q+UHinE=
=SXRz
-----END PGP SIGNATURE-----

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




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