Submitted by sgrayban on Sat, 06/05/2010 - 10:41
The debian security group has changed the way bind is installed - it's no longer chrooted and the package upgrade from last night also changes the PID file location.
PIDFILE = /var/run/bind/run/named/named.pid
PID file is under chroot directory? NO
I believe all debian flavours are effected by this.. I know debian lenny is.
Status:
Closed (fixed)
Comments
Submitted by bamajr on Sat, 06/05/2010 - 12:05 Comment #1
Yeah, I installed the BIND update, and now BIND will not start. I tried to start it manually via the Virtualmin Control Panel, but it says "Failed to start service : Failed to start BIND : Unknown error"
How do we fix this?
Submitted by JamieCameron on Sat, 06/05/2010 - 14:11 Comment #2
That's annoying of Debian to change the location like this - however, the fix is pretty simple. Just go to 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
By the way, which file are you seeing that PIDFILE= line in?
Submitted by sgrayban on Sat, 06/05/2010 - 20:52 Comment #3
/etc/init.d/bind9
This is the 3rd time they have made changes without explaining why.
First they changed the pid locations then they switched to chroot then they go back to non-chroot and moved the pid location.
Makes you wonder if we need to donate money to them so they can get a better quality of herb.
Submitted by bamajr on Sat, 06/05/2010 - 21:02 Comment #4
Jamie
There is no Module Config in Webmin -> Servers -> BIND DNS Server!
Submitted by bamajr on Sat, 06/05/2010 - 23:45 Comment #5
Wow, don't know why, but I was missing the Module Config. I swear it wasn't there, but after about 10 times refreshing the page, NOW I SEE IT :-)
Probably there all along!
Submitted by bamajr on Sat, 06/05/2010 - 23:50 Comment #6
The "Default PID file location(s)" on my system, after the BIND update read:
/var/run/bind/run/named.pid /var/run/named.pid
I just added the suggested /var/run/bind/run/named/named.pid change to the end of the line.
The "Default PID file location(s)" on my system, now reads:
/var/run/bind/run/named.pid /var/run/named.pid /var/run/bind/run/named/named.pid
... and it works just fine!
Submitted by sgrayban on Sun, 06/06/2010 - 00:03 Comment #7
The other locations aren't used in debian just /var/run/bind/run/named/named.pid
Submitted by JamieCameron on Sun, 06/06/2010 - 00:28 Comment #8
Yes, you can either add /var/run/bind/run/named/named.pid to the end, or just set the field to that path.
Submitted by sgrayban on Sun, 06/06/2010 - 00:37 Comment #9
It seems that the pid location is semi-hardcoded in the init.d file. I tried setting it in the options but that seems to be ignored now.
I am still trying to find out why debian made this radical change in the first bloody place.
Submitted by bamajr on Sun, 06/06/2010 - 11:33 Comment #10
Jamie
Can you check for an email from bamajr@sapphiresolutionsltd.com?
I've sent a couple and they never seem to get a response!!!
also, can you look at https://www.virtualmin.com/node/14472
Submitted by Rogi on Tue, 06/08/2010 - 13:12 Comment #11
"It seems that the pid location is semi-hardcoded in the init.d file. I tried setting it in the options but that seems to be ignored now."
How did you fis this sgrayban?
Setting it in the options is not working for me either.
Jamie, an update (very soon) for Virtualmin to fix this automatically would be a good idea?
Submitted by sgrayban on Tue, 06/08/2010 - 13:15 Comment #12
Read comment #2
Submitted by Rogi on Tue, 06/08/2010 - 13:21 Comment #13
No, as I just said, that is not working for me.
Submitted by sgrayban on Tue, 06/08/2010 - 13:27 Comment #14
did you also do step
PID file is under chroot directory? NO
Submitted by Rogi on Tue, 06/08/2010 - 13:29 Comment #15
Yes, and I still get this in syslog:
Jun 8 18:20:27 server1 named[21025]: none:0: open: /etc/bind/rndc.key: permission denied Jun 8 18:20:27 server1 named[21025]: couldn't add command channel 127.0.0.1#953: permission denied Jun 8 18:20:27 server1 named[21025]: none:0: open: /etc/bind/rndc.key: permission denied Jun 8 18:20:27 server1 named[21025]: couldn't add command channel ::1#953: permission denied Jun 8 18:20:27 server1 named[21025]: couldn't open pid file '/var/run/bind/run/named/named.pid': Permission denied Jun 8 18:20:27 server1 named[21025]: exiting (due to early fatal error)
Submitted by sgrayban on Tue, 06/08/2010 - 13:30 Comment #16
Thats a permission issue and not related to this bug.
Fix the permissions
Submitted by Kether2 on Tue, 06/15/2010 - 18:21 Comment #17
The same problem again. new version of bind appeared in debian lenny repos, and after update I've got the same issue - bind is running correctly, but virtualmin doesn't recognize it.. Any ideas? location of PID has been changed again?
Submitted by sgrayban on Tue, 06/15/2010 - 23:22 Comment #18
Debian did it again !! Those @#!@$#@! assholes...
New pid file is at /var/run/bind/run/named.pid now.
Submitted by bamajr on Thu, 06/17/2010 - 10:50 Comment #19
I'm curious: This issue returned on my servers after the Webmin update. I watched the install/update process and didn't see any updates to Debian, but did see updates to BIND. So who is moving this around?
Submitted by sgrayban on Thu, 06/17/2010 - 13:34 Comment #20
Bind was updated Monday night.
Submitted by Issues on Thu, 07/01/2010 - 18:20 Comment #21
Automatically closed -- issue fixed for 2 weeks with no activity.