I noticed today that bind showed as not running in webmin. When i checked from console it was running properly.
This reminded me an old bug i filed 38236. Indeed it was the same problem. Configuration on Webmin BIND, PID file is under chroot directory was reset to yes , probably from an update. I changed it to no and it worked (pid is /var/run/named/named.pid which is not in chroot)
Recently, 3 weeks ago, to solve bug 42565 I was adviced to update to the latest bind module. After this update however bind showed as running. Only today i noticed the problem.
I recently updated also debian bind package as well (standard Debian 8 stable security update)
I am running BIND 9.9.5-9+deb8u7-Debian (Extended Support Version)
Can you look why this option is reset to yes?
Comments
Submitted by JamieCameron on Wed, 10/05/2016 - 18:37 Comment #1
A webmin module update will never change a config option like that - they are set only at install time, or if you change them manually.
Submitted by web_support@web... on Thu, 10/06/2016 - 08:29 Pro Licensee Comment #2
ok. After more investigation it seems that the option did not change. PID file is under chroot directory? was yes before. I was confused because i could not start bind from webmin (see bug 42567) Starting it from console it ignored option in /etc/default/bind
OPTIONS="-u bind -t /var/lib/named"and run outside jail and pid was written outside jail.
My problem is probably systemd ignoring /etc/default/bind on console
So you are right. You can close this one
Submitted by JamieCameron on Fri, 10/07/2016 - 16:23 Comment #3