Can't start named, please help

hories1 hories1 at umbc.edu
Tue Mar 12 18:41:23 UTC 2002


Jim , Found it!  error logging was not configured on this AIX box.  After I 
restarted the syslogd guess what I found:

497>more syslog
Mar 12 13:30:08 nocr named[9842]: starting BIND 9.2.0 -d11
Mar 12 13:30:08 nocr named[9842]: command channel listening on 127.0.0.1#953
Mar 12 13:30:08 nocr named[9842]: couldn't open pid file '/var/run/named.pid': 
A
 file or directory in the path name does not exist.
Mar 12 13:30:08 nocr named[9842]: exiting (due to early fatal error)

It's running, thanks for your patience.

Howard






>===== Original Message From Jim Reid <jim at rfc1035.com> =====
>>>>> "Howard" == hories1  <hories1 at umbc.edu> writes:
>
>    Howard> Thanks Jim, I've run the named-checkconf and it produced
>    Howard> no output. I assume that it found no errors.  I've removed
>    Howard> the rndc config clause from the named.conf since I'm not
>    Howard> using Secure Dynamic Update.
>
>Eh? The control channel for rndc has nothing to do with Secure Dynamic
>Update. By deleting this, it looks like you're making the name server
>look for a non-existent file. And once it finds that file doesn't
>exist, it's game over.....
>
>    Howard> Mar 12 09:35:37.161 dns_master_load: db.cache:9: $TTL 2884515328
> MAXTTL, setting $TTL to 0
>
>You should fix this, though it's not fatal. BIND9 checks the TTL is no
>more than 2**31-1 (2147483647).
>
>    Howard> Mar 12 09:35:37.217 none:0: open: /etc/rndc.key: file not found
>
>This is probably a fatal error. Try setting up a valid controls{}
>statement in named.conf. Use rndc-confgen if you can't follow the
>documentation.



More information about the bind-users mailing list