Submitted by brucelet on Mon, 12/05/2011 - 18:31
I updated Virtualmin packages, including BIND and now BIND will not restart. I get this message:
Failed to start service : Failed to start BIND : Starting named: [FAILED]
Any clues to fix this? Kind of urgent, as the sites use our DNS server.
Status:
Closed (fixed)
Comments
Submitted by andreychek on Mon, 12/05/2011 - 18:35 Comment #1
Howdy -- after attempting to start BIND, take a look in /var/log/messages to see the errors that BIND is generating. It should just be a matter of correcting those in order to get BIND working.
Submitted by brucelet on Mon, 12/05/2011 - 18:53 Comment #2
It was saying it was a problem creating named.pid because it existed, so I removed it. Now it says there is no permission to create the pid file.
Submitted by brucelet on Mon, 12/05/2011 - 19:07 Comment #3
OK. I have another Virtuamin system and started comparing setups for BIND. I found the the named.pid was in /var/run on the other box, so I changed the named.conf on this server to put it in /var/run/named.pid and now BIND restarted. I'm not sure why it was thinking it was in /var/named, but now it works.
Aren't computers the greatest?
Thanks.
Submitted by andreychek on Mon, 12/05/2011 - 19:45 Comment #4
That's an unusual problem, but I'm glad you got it figured out! Thanks for letting us know how you fixed it.
Submitted by stels88 on Thu, 12/08/2011 - 10:03 Comment #5
that can be related to package/os version + sometimes that happen when peoples adding 3rd party repositories for package managers.
Submitted by Issues on Thu, 12/22/2011 - 10:18 Comment #6
Automatically closed -- issue fixed for 2 weeks with no activity.