BIND will not start

I just ran a bunch of Virtualmin updates and now BIND will not restart, it just errors out. Any thoughts?

Status: 
Active

Comments

What errors do you receive when trying to start BIND?

If there's none on the command line, you may want to take a peek in /var/log/syslog for any errors that may be showing up.

Failed to start BIND : Starting named: [FAILED]

Also, check what errors get logged to /var/log/messages when you try to start BIND.

Yeah, that error doesn't give much info about what the actual problem is... what error do you see when looking in /var/log/syslog?

Oops, Jamie is right... /var/log/syslog is just for Debian/Ubuntu based systems, the error message you want would be in /var/log/messages on your CentOS server :-)

A couple of things of note in messages:

  1. max open files (1024) is less than max sockets (4096)
  2. could not configure root hints from /etc/db.cache, file not found.

Then it says loading configuration, file not found. Exiting, due to fatal errors.

Do you want access to the system? Jamie, it's the same bruce/root login as before.

Did you get the login info?

I logged in and got it started ... there were several problems, such as /var/named/chroot/etc/db.cache being missing , and the directory /var/named/chroot/var/named not being writable by the named user.

Could you look into my just submitted ticket #17017 - it sounds like a very similar issue.