LSB bind startup script broken.

[Hendrik Visage]

Hi there,

 I consistently get the following errors when I
try to startup named/bind from /etc/init.d/named
(the lsb thingy):

#/etc/init.d/named start
(syslog messages:)
Jun 11 10:00:42 [named] starting BIND 9.2.2 -u bind
Jun 11 10:00:42 [named] using 1 CPU
Jun 11 10:00:42 [named] loading configuration from '/etc/named.conf'
Jun 11 10:00:42 [named] no IPv6 interfaces found
Jun 11 10:00:42 [named] listening on IPv4 interface lo, 127.0.0.1#53
Jun 11 10:00:42 [named] listening on IPv4 interface eth0, 196.36.161.89#53
Jun 11 10:00:42 [named] listening on IPv4 interface eth1, 196.36.168.58#53
Jun 11 10:00:42 [named] zone 'envisage.co.za' allows updates by IP address, whic
h is insecure
Jun 11 10:00:42 [named] zone '168.36.196.hvisage.168.36.196.in-addr.arpa.' allow
s updates by IP address, which is insecure
Jun 11 10:00:42 [named] command channel listening on 127.0.0.1#953
Jun 11 10:00:42 [named] couldn't open pid file '/var/run/named.pid': File exists
Jun 11 10:00:42 [named] exiting (due to early fatal error)

Then I remove /var/run/named.pid and again do a /etc/init.d/named start

Jun 11 10:01:34 [named] starting BIND 9.2.2 -u bind
Jun 11 10:01:34 [named] using 1 CPU
Jun 11 10:01:34 [named] loading configuration from '/etc/named.conf'
Jun 11 10:01:34 [named] no IPv6 interfaces found
Jun 11 10:01:34 [named] listening on IPv4 interface lo, 127.0.0.1#53
Jun 11 10:01:34 [named] listening on IPv4 interface eth0, 196.36.161.89#53
Jun 11 10:01:34 [named] listening on IPv4 interface eth1, 196.36.168.58#53
Jun 11 10:01:34 [named] zone 'envisage.co.za' allows updates by IP address, whic
h is insecure
Jun 11 10:01:34 [named] zone '168.36.196.hvisage.168.36.196.in-addr.arpa.' allow
s updates by IP address, which is insecure
Jun 11 10:01:34 [named] command channel listening on 127.0.0.1#953
Jun 11 10:01:34 [named] couldn't open pid file '/var/run/named.pid': File exists
Jun 11 10:01:34 [named] exiting (due to early fatal error)

Then a plain old: named (Not using the startup script in other words)

Jun 11 10:01:41 [named] starting BIND 9.2.2
Jun 11 10:01:41 [named] using 1 CPU
Jun 11 10:01:41 [named] loading configuration from '/etc/named.conf'
Jun 11 10:01:41 [named] no IPv6 interfaces found
Jun 11 10:01:41 [named] listening on IPv4 interface lo, 127.0.0.1#53
Jun 11 10:01:41 [named] listening on IPv4 interface eth0, 196.36.161.89#53
Jun 11 10:01:41 [named] listening on IPv4 interface eth1, 196.36.168.58#53
Jun 11 10:01:41 [named] zone 'envisage.co.za' allows updates by IP address, whic
h is insecure
Jun 11 10:01:41 [named] zone '168.36.196.hvisage.168.36.196.in-addr.arpa.' allow
s updates by IP address, which is insecure
Jun 11 10:01:41 [named] command channel listening on 127.0.0.1#953
Jun 11 10:01:41 [named] logging channel 'an_example_channel' file '/tmp/example.
log': permission denied

etc. showing the server have successfully started.

This is the second server that's doing this to me.

Hendrik