I am running:
Operating system CentOS Linux 5.3
Webmin version 1.470
Virtualmin version 3.69.gpl GPL
Theme version 7.1
Kernel and CPU Linux 2.6.18-128.1.10.el5 on i686
My bind wont start, was working fine then virtualmin did a upgrade I think for Ruby and Python.
did not complete it I think.
I then later noticed that Bind was not working
Now wont start Bind says:
Failed to start service : Failed to start BIND : Starting named: [FAILED]
If I log into my domain via the ip address and run under bind server “Check BIND Config”
says:
No errors were found in the BIND configuration file /var/named/chroot/etc/named.conf or referenced zone files.
saw this command used on one thread not sure if it helps.
ps auxw | grep named
gives
ps auxw | grep named
root 11900 0.0 0.2 2448 1020 ? S 14:21 0:00 sh -c su root -c ps\ auxw\ |\ grep\ named 2>&1
root 11901 0.0 0.2 2832 1104 ? S 14:21 0:00 su root -c ps auxw | grep named
root 11902 0.0 0.1 2404 900 ? S 14:21 0:00 bash -c ps auxw | grep named
Does not give the same reslts as they had.
Also where can I find an error log for bind as the error message I got helps me zero.
Yeah, it sounds like something is awry with your logging – as /var/log/messages should exist on all servers.
In the meantime, however, try running this command to try and coax BIND to show you some error messages:
/usr/sbin/named -u named -f -g
Then, paste in the output you see on the console, that will hopefully show what the issue there is.
I do agree with Ronald, though, in that I’d recommend upgrading Virtualmin… keeping up with software updates is important, and the version you’re running has some security issues in it
Its been running the command now for about 8 minutes with no output yet,
I noticed that my email suddenly downloaded a few emails from this domain, not many usually gets quite alot, but when I checked it still showed stopped in the system info summary.
but when I tried to start Bind now I got a different error
Failed to start service : Failed to start BIND : Starting named: named: already running[FAILED]
Failed to start service : Failed to start BIND : Starting named: named: already running[FAILED]
Yeah, that message there suggests that BIND had already been started.
As for what happened to cause all that – I honestly have no idea That’s all very unusual, and the idea that the server doesn’t have logging available in /var/log/messages is equally odd.
Also, the command I gave you should not have fixed it, it should just have temporarily enabled some debugging info. It didn’t even work, actually, as the error message above suggests BIND was already running when you ran that
So it sounds like something you did got things running…