On 1/24/11 12:33 PM, Gary Kline wrote:
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.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?
_______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[email protected]"
