Re: rndc: connect failed: connection refused

On Sun, Oct 17, 2004 at 06:23:09PM +0100, Greg Mathews wrote:
> Gregory
>
> This is what I can't understand, if I manually start named using the command
>
> named -u named
>
> I get the following messages
>
> Oct 17 18:21:21 dedi5 named[6169]: starting BIND 9.2.2 -u named
> Oct 17 18:21:21 dedi5 named[6169]: using 1 CPU
> Oct 17 18:21:21 dedi5 named[6169]: loading configuration from '/etc/named.conf'
> Oct 17 18:21:21 dedi5 named[6169]: no IPv6 interfaces found
> Oct 17 18:21:21 dedi5 named[6169]: listening on IPv4 interface eth0,
> 123.123.123.123#53
> Oct 17 18:21:21 dedi5 named[6169]: listening on IPv4 interface eth0:2,
> 124.124.124.124#53
> Oct 17 18:21:21 dedi5 named[6169]: command channel listening on 127.0.0.1#953
>
> if I then restart using the command
>
> /etc/rc.d/init.d/named restart
>
> I just get
>
> Oct 17 18:21:31 dedi5 named[6183]: starting BIND 9.2.1 -u named
> Oct 17 18:21:31 dedi5 named[6183]: using 1 CPU
> Oct 17 18:21:31 dedi5 named: named startup succeeded
>
> If I then do
>
> ps aux|grep named
>
> it returns no running processes and named is not running
>
> I note that it doesn't appear to be loading the conf file when using the
> startup script

-d debug-level Set the daemons debug level to debug-level.
Debugging traces from named become more verbose as the
debug level increases.
-f Run the server in the foreground (i.e. do not daemonize).
-g Run the server in the foreground and force all logging
to stderr.

I beleave one of these flags will help. Especialy the -d. I've used it
to make the process more verbose so I could trace problems and find out
where the issue lies when bind wasn't working properly for me. Another
tool at your disposal is strace and it'll print output to stdout.

Jerry M. Howell II