O I had to have my OS rebuild, I restored everything from backups and the only thing I cant get going is my darn nameserver. I know this is not the right section, but since everyone is chekcing it I would apprisate it being left here for the day (please)...lol
I get the following when trying to start the name server
named has failed, please contact the sysadmin (result was "named is not running").
Jun 6 12:00:06 zeustwo named[18368]: starting BIND 9.5.0 -u named
Jun 6 12:00:06 zeustwo named[18368]: found 4 CPUs, using 4 worker threads
Jun 6 12:00:06 zeustwo named[18368]: loading configuration from '/etc/named.conf'
Jun 6 12:00:06 zeustwo named[18368]: the working directory is not writable
Jun 6 12:00:06 zeustwo named[18368]: listening on IPv4 interface lo, 127.0.0.1#53
Jun 6 12:00:06 zeustwo named[18368]: listening on IPv4 interface eth0, 75.125.245.146#53
Jun 6 12:00:06 zeustwo named[18368]: listening on IPv4 interface eth0:1, 75.125.245.147#53
Jun 6 12:00:06 zeustwo named[18368]: listening on IPv4 interface eth0:2, 75.125.245.148#53
Jun 6 12:00:06 zeustwo named[18368]: listening on IPv4 interface eth0:3, 75.125.245.149#53
Jun 6 12:00:06 zeustwo named[18368]: listening on IPv4 interface eth0:4, 75.125.245.150#53
Jun 6 12:00:06 zeustwo named[18368]: listening on IPv4 interface eth0:5, 75.125.245.151#53
Jun 6 12:00:06 zeustwo named[18368]: listening on IPv4 interface eth0:6, 75.125.245.152#53
Jun 6 12:00:06 zeustwo named[18368]: listening on IPv4 interface eth0:7, 75.125.245.153#53
Jun 6 12:00:06 zeustwo named[18368]: listening on IPv4 interface eth0:8, 75.125.245.154#53
Jun 6 12:00:06 zeustwo named[18368]: listening on IPv4 interface eth0:9, 75.125.245.155#53
Jun 6 12:00:06 zeustwo named[18368]: listening on IPv4 interface eth0:10, 75.125.245.156#53
Jun 6 12:00:06 zeustwo named[18368]: listening on IPv4 interface eth0:11, 75.125.245.157#53
Jun 6 12:00:06 zeustwo named[18368]: listening on IPv4 interface eth0:12, 75.125.245.158#53
Jun 6 12:00:06 zeustwo named[18368]: default max-cache-size (33554432) applies
Jun 6 12:00:06 zeustwo named[18368]: automatic empty zone: 0.IN-ADDR.ARPA
Jun 6 12:00:06 zeustwo named[18368]: automatic empty zone: 127.IN-ADDR.ARPA
Jun 6 12:00:06 zeustwo named[18368]: automatic empty zone: 254.169.IN-ADDR.ARPA
Jun 6 12:00:06 zeustwo named[18368]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Jun 6 12:00:06 zeustwo named[18368]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Jun 6 12:00:06 zeustwo named[18368]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Jun 6 12:00:06 zeustwo named[18368]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Jun 6 12:00:06 zeustwo named[18368]: automatic empty zone: D.F.IP6.ARPA
Jun 6 12:00:06 zeustwo named[18368]: automatic empty zone: 8.E.F.IP6.ARPA
Jun 6 12:00:06 zeustwo named[18368]: automatic empty zone: 9.E.F.IP6.ARPA
Jun 6 12:00:06 zeustwo named[18368]: automatic empty zone: A.E.F.IP6.ARPA
Jun 6 12:00:06 zeustwo named[18368]: automatic empty zone: B.E.F.IP6.ARPA
Jun 6 12:00:06 zeustwo named[18368]: default max-cache-size (33554432) applies: view _bind
Jun 6 12:00:06 zeustwo named[18368]: command channel listening on 127.0.0.1#953
Jun 6 12:00:06 zeustwo named[18368]: couldn't open pid file '/usr/var/run/named.pid': File exists
Jun 6 12:00:06 zeustwo named[18368]: exiting (due to early fatal error)
I have tried to stop all the name servers from root
delete the pid
and start named back up and then I get Cant Find File named.pid
If I start it again, I get the same error messages as before.
The folder /usr/var/run is owned by root as well as the file named.pid when it does get created.
I have google th error and only found 3 referances to it
Any thoughts?
Z