Really, the best way to determine whether or not named is running is "ps ax | grep named" or "service named status".
And even then, "service named restart" should work...even if named wasn't running, in the first place, it would be started, assuming that it was not, already. The errors you got indicate that named was, indeed, running at the time. The named.pid error can be explained away if the system had crashed and named hadn't shut down, properly, but if port 953 was already open, chances are that named was actually running. Something to consider, with regard to the timeout issue, is this: If you have done the right thing and set up a secondary DNS server, that is off your network, then it is possible that even if you query the domain from the primary DNS server, your system could be trying to obtain its answer from the secondary. On Thu, 26 Sep 2002, Maria Kelly wrote: > > Hello > I read with interest the correspondance regarding named as I was having the same >problem myself. I followed the advice given and seem to have resolved the issue I >think. However if someone would could clarify what is going on with the following I >would be grateful. I can't figure it out from the documentation. > > On booting machine and running named -g I get the output listed previously > > couldn't open pid file /var/run/named/named.pid': Permission denied > exiting due to fatal error > I get the same with /usr/sbin/named > > To confirm it wasn't running I ran dig www.tcd.ie and got connection timed out, no >server could be reached > > I then ran /sbin/services named start as suggested in your discussion > named -g gave the following output > > starting Bind 9.2.0 -g > using 1 CPU > loading configuration from '/etc/named/conf' > no IPv6 interfaces found > listening on IPv4 onterface lo 127.0.0.1#53 > binding TCP socket: address in use > listening on IPv4 onterface lo xxx.x.xxx.xxx#53 > binding TCP socket: address in use > /etc/named/conf:19 couldn't add command channel 127.0.0.1#953:address in use > ignoring config file logging statement due to -g option > couldn't open pid file '/var/run/named/named.pid': File exists > exiting (due to early fatal error) > > At this stage I thought named had failed to start however > dig www.tcd.ie came back with an answer and came back much faster as expected second >time round. > So really what I want to know is can I assume named is working as expected. I think >it is. > What is the above error message about? > Should I be worried about command channel #953? > > > Any information appreciated > > Thanks > > Maria > > > email [EMAIL PROTECTED] > _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
