Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Jan 2011 14:03:52 -0700
From:      Jarrod Slick <jarrod.sl@gmail.com>
To:        Gary Kline <kline@thought.org>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: questions on bind9-3.6-P1
Message-ID:  <4D3DE938.9000503@gmail.com>
In-Reply-To: <20110124204804.GA60244@thought.org>
References:  <20110124193325.GA59781@thought.org> <4D3DD582.6040004@gmail.com> <20110124204804.GA60244@thought.org>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 1/24/11 1:48 PM, Gary Kline wrote:
> On Mon, Jan 24, 2011 at 12:39:46PM -0700, Jarrod Slick wrote:
>> On 1/24/11 12:33 PM, Gary Kline wrote:
>>> 	oKay, since my prev question caught no wixards, how about looking at
>>> 	the errors from bind-9.3.6? [I rebuilt this from the src tarball; it
>>> 	finally installed; I fixed some obvious errors, but several remain.
>>>
>>> 	Here is the log file where bind9 fails on "em0", my NIC in my server.
>>> 	This is one failure that is simply over my head.
>>>
>>> +++
>>>
>>> Jan 24 11:14:55 ethic named[59747]: starting BIND 9.3.6-P1 -c
>>> /var/named/etc/namedb/named.conf
>>> Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket:
>>> address in use
>>> Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface em0 failed;
>>> interface ignored
>>> Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket:
>>> address in use
>>> Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface lo0 failed;
>>> interface ignored
>>> Jan 24 11:14:55 ethic named[59747]: not listening on any interfaces
>>> Jan 24 11:14:55 ethic named[59747]: couldn't add command channel
>>> 127.0.0.1#953: address in use
>>> Jan 24 11:14:55 ethic named[59747]: couldn't add command channel ::1#953:
>>> address in use
>>> Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket:
>>> address in use
>>> Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface em0 failed;
>>> interface ignored
>>> Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket:
>>> address in use
>>> Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface lo0 failed;
>>> interface ignored
>>> Jan 24 11:14:55 ethic named[59747]: running
>>> +++
>>>
>>> 	Can anybody explain why (eg) the lo0 failed or was ignored.  And
>>> 	why bind9--now offically at its EOLife--has trouble creating an
>>> 	IPv4 interface with my NIC, em0?  Do I have to do some very simple?
>>> 	like rebooting?
>>>
>>>
>>>
>>>
>>>
>> I think the issue probably lies in the "address in use" part of your
>> error output.  Try a sockstat/netstat to see what's bound on port 953.
>> If it's an old instance of bind, kill it and then try restarting.
>>
>
> HMMM: Here's what the log shows:
>
> --sorry for the overage; i cannot cut/paste here on ethic].  Looks like same
> thing.
>
>
> Jan 24 12:14:56 ethic named[59747]: creating IPv4 interface lo0 failed; interface ignored
> Jan 24 12:14:56 ethic named[59747]: not listening on any interfaces
> Jan 24 12:15:09 ethic root: Unknown USB device: vendor 0x17f6 product 0x0709 bus uhub4
> Jan 24 12:15:09 ethic kernel: ukbd1:<Unicomp Endura Keyboard, class 0/0, rev 1.10/2.15, addr 4>  on uhub4
> Jan 24 12:15:09 ethic kernel: kbd3 at ukbd1
> Jan 24 12:15:39 ethic sm-mta[60106]: p0OKD6D2060106: SYSERR(root): collect: I/O error on connection from mx2.freebsd.org, from=<owner-freebsd-hackers@freebsd.org>
> Jan 24 12:33:50 ethic ntpd[862]: kernel time sync status change 6001
> Jan 24 12:37:04 ethic named[60266]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf
> Jan 24 12:37:04 ethic named[60266]: could not listen on UDP socket: address in use
> Jan 24 12:37:04 ethic named[60266]: creating IPv4 interface em0 failed; interface ignored
> Jan 24 12:37:04 ethic named[60266]: could not listen on UDP socket: address in use
> Jan 24 12:37:04 ethic named[60266]: creating IPv4 interface lo0 failed; interface ignored
> Jan 24 12:37:04 ethic named[60266]: not listening on any interfaces
> Jan 24 12:37:04 ethic named[60266]: couldn't add command channel 127.0.0.1#953: address in use
> Jan 24 12:37:04 ethic named[60266]: couldn't add command channel ::1#953: address in use
> Jan 24 12:37:04 ethic named[60266]: could not listen on UDP socket: address in use
> Jan 24 12:37:04 ethic named[60266]: creating IPv4 interface em0 failed; interface ignored
> Jan 24 12:37:04 ethic named[60266]: could not listen on UDP socket: address in use
> Jan 24 12:37:04 ethic named[60266]: creating IPv4 interface lo0 failed; interface ignored
> Jan 24 12:37:04 ethic named[60266]: running
>
>> _______________________________________________
>> freebsd-questions@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
Okay, but what exactly did you do?  I guess my instruction to, 
"restart," was a bit ambiguous.  I meant after killing whatever is 
running on port 953 you should restart __bind__, preferably by executing 
your desired binary manually, not the system itself.  You may be 
executing two instances of bind at startup as another respondent suggested.

To recap, see what's bound on port 953:

netstat -ntpl | grep 953

kill whatever is bound on 953 (you should be able to get the pid from 
the netstat output)

kill -9 <PID>

start your desired named:

/path/to/bind <your_arguments>

If that leaves you with a working named installation, remove the 
extraneous startup script and reboot to confirm that your issue is fixed.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?4D3DE938.9000503>