virtualmin reporting BIND isn't started, yet it is

Virtualmin
1

Hi,

I’m pretty sure this is a common problem… so sorry in advance if tyhis question’s been asked before
I found some similar problems, yet none of those threads were able to solve my problem.

When i browse to my virtualmin page, it shows me bind isn’t started. yet i’m very positive it IS started:

bind 19188 0.0 2.7 115820 13500 ? Ssl 16:39 0:00 /usr/sbin/named -u bind

plus, it’s working :stuck_out_tongue:

when i try to “start bind”, it gives me an unknown error, restarting bind doesn’t solve the problem.

now, where should i start looking?
thanks guys!

2

Are you by chance using Debian?

A recent Debian update to BIND seems to have caused some trouble…

Due to the changes they made, Virtualmin may not be able to determine that BIND is running (even though it’s running just fine). There’s a bugreport here regarding that:

http://www.virtualmin.com/node/14569

A quick fix would be to go into Webmin -> Servers -> BIND DNS Server -> Module Config -> System configuration, and change the “Default PID file location(s)” to /var/run/bind/run/named/named.pid

After that, it should show as running again.

-Eric

3

yup, that was it…
perhaps I should start reading changelogs… :slight_smile:

thx Eric!

4

This should be set as a sticky post as I am still reading duplicate bug reports.

Seriously users !!! Before posting bug reports do a search and see if it has been answered already.