On Mon, Jan 24, 2011 at 02:45:41PM -0500, Jon Radel wrote:
> On 1/24/11 2: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?
> >
> 
> It appears to be complaining that you're already running another piece 
> of software that is listening
> on all those ports.  I'd be guessing another copy of bind.  Try:
> 
> ps uxwwa | grep named
> 
> and see what all is running.  If you're dealing with a bind from base 
> and bind from ports I could
> see you trying to start both of them.  Do you have named files in both 
> /etc/rc.d and /usr/local/etc/rc.d?
> 
> -- 
> 
> --Jon Radel
> j...@radel.com
> 
> 

        There is only one /etc/rc.d/named script; in fact, I have neven seen
        one from bind9-3 or bind9-7 [in /usr/local/etc/rc.d].

        You're right about dup instances of named going!  I'll kill9 and 
        see what happens when i restart.


Jan 24 12:37:04 ethic named[60266]: creating IPv4 interface lo0 failed; 
interface ignored
Jan 24 12:37:04 ethic named[60266]: running
Jan 24 12:59:32 ethic named[60411]: starting BIND 9.3.6-P1 -c 
/var/named/etc/namedb/named.conf
Jan 24 12:59:32 ethic named[60411]: command channel listening on 127.0.0.1#953
Jan 24 12:59:32 ethic named[60411]: command channel listening on ::1#953
Jan 24 12:59:32 ethic named[60411]: running


        You're good, Jon!

        Somebody mentioned this yesterday but i had already KILLED my named.
        Just by script.   So, should I follow the FBSD tradition of: if it
        works, why upgrade? Or should I try buind97 again?

        .... tHe reason for all this caution is that bind97 output a trucloak
        of errors that well way the hell over my head.  And I really do need
        UDP.

        gary



-- 
 Gary Kline  kl...@thought.org  http://www.thought.org  Public Service Unix
    The 7.97a release of Jottings: http://jottings.thought.org/index.php
                           http://journey.thought.org
                                     ethic 
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to