BIND9 on 4.10: couldn't open pid file: permission denied

[Erik Norgaard]

Hi,

I had a working BIND9 running but needed to restart after updating the
zone file with the following command:

# /usr/local/sbin/named -g -u bind -t /var/named -c /etc/named.conf

But this failed:

Nov 10 12:23:58.110 starting BIND 9.2.3 -g -u bind -t /var/named -c
/etc/named.conf
Nov 10 12:23:58.111 using 1 CPU
Nov 10 12:23:58.118 loading configuration from '/etc/named.conf'
Nov 10 12:23:58.120 listening on IPv4 interface vr0, 192.168.0.4#53
Nov 10 12:23:58.121 listening on IPv4 interface vr1, 10.0.0.1#53
Nov 10 12:23:58.122 listening on IPv4 interface lo0, 127.0.0.1#53
Nov 10 12:23:58.132 none:0: open: /usr/local/etc/rndc.key: file not found
Nov 10 12:23:58.133 couldn't add command channel 127.0.0.1#953: file not
found
Nov 10 12:23:58.133 none:0: open: /usr/local/etc/rndc.key: file not found
Nov 10 12:23:58.133 couldn't add command channel ::1#953: file not found
Nov 10 12:23:58.134 could not open entropy source /dev/random: file not
found
Nov 10 12:23:58.134 ignoring config file logging statement due to -g option
Nov 10 12:23:58.134 couldn't open pid file '/var/run/named.pid':
Permission denied
Nov 10 12:23:58.134 exiting (due to early fatal error)

The odd thing is the directories have the following permissions:

drwxrwxr-x  6 bind  bind    512 Jun 24 11:16 var

var:
drwxrwxr-x  3 bind  bind  512 Jun 24 11:16 log
drwxrwxr-x  3 bind  bind  512 Nov 10 11:53 run
drwxrwxr-x  3 bind  bind  512 Jun 24 11:16 tmp

and there is no named.pid file in run with other owner ship messing
things up.

I can start named with '-u root' but I'd rather not.

Any suggestions?

Thanks, Erik
-- 
Ph: +34.666334818                                  web: www.locolomo.org
S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt
Subject ID:  A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9
Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2