debian bind update new bug

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

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?

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?

/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.

Jamie

There is no Module Config in Webmin -> Servers -> BIND DNS Server!

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!

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!

The other locations aren't used in debian just /var/run/bind/run/named/named.pid

Yes, you can either add /var/run/bind/run/named/named.pid to the end, or just set the field to that path.

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.

"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?

No, as I just said, that is not working for me.

did you also do step

PID file is under chroot directory? NO

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)

Thats a permission issue and not related to this bug.

Fix the permissions

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?

Debian did it again !! Those @#!@$#@! assholes...

New pid file is at /var/run/bind/run/named.pid now.

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?

Bind was updated Monday night.

Automatically closed -- issue fixed for 2 weeks with no activity.