RHE3+Plesk 8+up2date=death and destruction of bind.

[carliebentley]

up2date worked well on everything except Bind.

Which it completely destroyed.

I'm struggling with the following:

Here's the message Log:

--
starting BIND 9.2.4
Sep 25 22:39:28 server named[15331]: using 1 CPU
Sep 25 22:39:28 server named[15331]: loading configuration from '/etc/named.conf'
Sep 25 22:39:28 server named[15331]: no IPv6 interfaces found
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface lo, 127.0.0.1#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface eth0, 67.15.14.68#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface eth0:1, 67.15.15.210#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface eth0:2, 67.15.15.211#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface eth0:3, 67.15.15.212#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface eth0:4, 67.15.15.213#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface eth0:5, 67.15.15.214#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface eth0:6, 67.15.15.215#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:28 server named[15331]: listening on IPv4 interface eth0:7, 67.15.15.216#53
Sep 25 22:39:28 server named[15331]: binding TCP socket: address in use
Sep 25 22:39:29 server named[15331]: command channel listening on 127.0.0.1#953
Sep 25 22:39:29 server named[15331]: couldn't open pid file '/var/run/named/named.pid': Permission denied
Sep 25 22:39:29 server named[15331]: exiting (due to early fatal error)
--


Here's the opening portion of named.conf

options {
allow-recursion {
localnets;
};
directory "/var";
auth-nxdomain no;
pid-file "/var/run/named/named.pid";
};

//Use with the following in named.conf, adjusting the allow list as needed:

key "rndc-key" {
algorithm hmac-md5;
secret "XXXXXXXXXXXXXXXXXXXXXXI know this is rightXXXXXXXXX";
};
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "rndc-key"; };
};


Then it starts detailing the zones.
--

Here's the rndc.conf

options {
default-server localhost;
default-key "rndc-key";
};

server localhost {
key "rndc-key";
};

key "rndc-key" {
algorithm hmac-md5;
secret "XXXXXXXXXXXXXXXXXXXXXXI know this is rightXXXXXXXXX";
};

--

And just to make certain here's the rndc.key

key "rndc-key" {
algorithm hmac-md5;
secret "XXXXXXXXXXXXXXXXXXXXXXI know this is rightXXXXXXXXX";
};

--

And Yet I still get the following error when I try to launch named.

Sep 25 22:39:29 server named[15331]: couldn't open pid file '/var/run/named/named.pid': Permission denied
Sep 25 22:39:29 server named[15331]: exiting (due to early fatal error)


If I ever get this fixed, I may not open an ssh terminal again. It's really very frustrating.

 

[breun]

The problem is probably bind-chroot (which shouldn't be installed):

# rpm -e bind-chroot
# ln -s /var/named/run-root/etc/named.conf /etc/named.conf
# service named start