Theinit for bind /etc/init.d/named sets PIDFILE="/var/run/named/named.pid" when bind is not run chrooted. The value is not being used and bind is trying to write named.pid to /var/run as named:named and it does not have permission to write there. Thus, it fails to start. Reproducible: Always Steps to Reproduce: 1.install bind 9.2.2-r4 and edit named and zone files, do not enable chroot 2.start bind (/etc/init.d/named start) 3. Actual Results: Sep 28 16:11:12 chipmunk named[6924]: loading configuration from '/etc/bind/named.conf' Sep 28 16:11:12 chipmunk named[6924]: listening on IPv4 interface eth0, xxx.xxx.xxx.xxx#53 Sep 28 16:11:12 chipmunk process `named' is using obsolete setsockopt SO_BSDCOMPAT Sep 28 16:11:12 chipmunk named[6924]: listening on IPv4 interface lo, 127.0.0.1#53 Sep 28 16:11:12 chipmunk named[6924]: command channel listening on 127.0.0.1#953 Sep 28 16:11:12 chipmunk named[6924]: couldn't open pid file '/var/run/named.pid': Permission denied Sep 28 16:11:12 chipmunk named[6924]: exiting (due to early fatal error) Expected Results: named.pid should be written to /var/run/named/naemd.conf as set in /etc/init.d/named: if [ $CHROOT -a -d $CHROOT ] ; then PIDFILE="${CHROOT}/var/run/named/named.pid" KEY="${CHROOT}/etc/bind/rndc.key" else PIDFILE="/var/run/named/named.pid" KEY="/etc/bind/rndc.key" fi I've run strace, but am not sure what to look for in it
*** Bug 65886 has been marked as a duplicate of this bug. ***
I have the same problem Has the bug been fixed? Can the status be updated? thanks
I have found a solution to this problem You need to put the following lines in the named.conf : options { pid-file "/var/run/named.pid"; };
in fact, bug was fixed somewhere around 9.2.3
