On 9/1/06, Johnny Hughes <mailing-lists@xxxxxxxxxxxx> wrote:
On Fri, 2006-09-01 at 05:02 -0500, Larry Vaden wrote: > On 9/1/06, Karanbir Singh <mail-lists@xxxxxxxxx> wrote: > > Larry Vaden wrote: > > > On 9/1/06, Karanbir Singh <mail-lists@xxxxxxxxx> wrote: > > >> > > >> look at the thread again, its only when someone does an update for only > > >> sqlite that they have an issue, a 'yum update yum; yum update' has > > >> worked fine for me > > > > > > chroot'd named quit running about 05:00 yesterday morning. wouldn't > > > restart due to permission problems. > > > > > > > have you opened a bug report for this ? > > There was something similar mentioned by others 08/13 regarding a > change released 08/11. I'm not sure why we weren't impacted until > yesterday ~ 05:00. > You were affected yesterday ... Because ... it was an update for 4.4. RH released 4.4 on 8/10 CentOS released the security updates included for 4.4 on 8/23 (bind was a bugfix update and not a security update ... it was not released on 8/23). CentOS released the full 4.4 update set on 8/29, and since bind was a bugfix updates and not secuirty update, that is when it was released. It is the CentOS goal to have the update set releases out 2 weeks after the update ... however due to a showstopper bug in 3.8 (the rescue CD would not work, and still does not work in the upstream product) we had to delay it's update and fix the problem. That delay caused a corresponding delay in releasing CentOS-4.4 since we can only release one major update set at a time due bandwidth considerations. So, CentOS-4.4 was released 8/29 ... and that was 5 days past our 14 day goal. THAT is why you saw the problem yesterday :)
Thanks for your explanation. I tried two or three differenct solutions without result, so because it was a production server (ns2), I resorted to changing the permissions. What is the correct solution? rgds/ldv log entries: Aug 31 05:42:08 ns2 named[1988]: shutting down: flushing changes Aug 31 05:42:08 ns2 named[1988]: stopping command channel on 127.0.0.1#953 Aug 31 05:42:08 ns2 named: succeeded Aug 31 05:42:09 ns2 named[1988]: exiting Aug 31 05:42:11 ns2 named[12127]: starting BIND 9.2.4 -u named -t /var/named/chroot Aug 31 05:42:11 ns2 named[12127]: using 1 CPU Aug 31 05:42:11 ns2 named: named startup succeeded Aug 31 05:42:11 ns2 named[12127]: loading configuration from '/etc/named.conf' Aug 31 05:42:11 ns2 named[12127]: no IPv6 interfaces found Aug 31 05:42:11 ns2 named[12127]: listening on IPv4 interface lo, 127.0.0.1#53 Aug 31 05:42:11 ns2 named[12127]: listening on IPv4 interface eth0, 209.151.96.66#53 Aug 31 05:42:11 ns2 named[12127]: zone version.bind/CH: has 0 SOA records Aug 31 05:42:11 ns2 named[12127]: zone version.bind/CH: has no NS records Aug 31 05:42:11 ns2 named[12127]: view.c:347: REQUIRE((&view->references)->refs > 0) failed Aug 31 05:42:11 ns2 named[12127]: exiting (due to assertion failure) Aug 31 05:44:32 ns2 named: failed Aug 31 05:44:34 ns2 named[12742]: starting BIND 9.2.4 -u named -t /var/named/chroot Aug 31 05:44:34 ns2 named[12742]: using 2 CPUs Aug 31 05:44:34 ns2 named[12742]: loading configuration from '/etc/named.conf' Aug 31 05:44:35 ns2 named[12742]: no IPv6 interfaces found Aug 31 05:44:35 ns2 named[12742]: listening on IPv4 interface lo, 127.0.0.1#53 Aug 31 05:44:35 ns2 named[12742]: listening on IPv4 interface eth0, 209.151.96.66#53 Aug 31 05:44:35 ns2 named[12742]: command channel listening on 127.0.0.1#953 Aug 31 05:44:35 ns2 named[12742]: couldn't open pid file 'named.pid': File exists Aug 31 05:44:35 ns2 named[12742]: exiting (due to early fatal error) Aug 31 05:44:35 ns2 named: named startup failed Aug 31 15:52:21 ns2 named: failed Aug 31 15:52:23 ns2 named[13133]: starting BIND 9.2.4 -u named -t /var/named/chroot Aug 31 15:52:23 ns2 named[13133]: using 2 CPUs Aug 31 15:52:23 ns2 named[13133]: loading configuration from '/etc/named.conf' Aug 31 15:52:23 ns2 named[13133]: no IPv6 interfaces found Aug 31 15:52:23 ns2 named[13133]: listening on IPv4 interface lo, 127.0.0.1#53 Aug 31 15:52:23 ns2 named[13133]: listening on IPv4 interface eth0, 209.151.96.66#53 Aug 31 15:52:23 ns2 named[13133]: command channel listening on 127.0.0.1#953 Aug 31 15:52:23 ns2 named[13133]: couldn't open pid file 'named.pid': File exists Aug 31 15:52:23 ns2 named[13133]: exiting (due to early fatal error) Aug 31 15:52:23 ns2 named: named startup failed Aug 31 15:54:05 ns2 named: failed Aug 31 15:54:07 ns2 named[13165]: starting BIND 9.2.4 -u named -t /var/named/chroot Aug 31 15:54:07 ns2 named[13165]: using 2 CPUs Aug 31 15:54:07 ns2 named[13165]: loading configuration from '/etc/named.conf' Aug 31 15:54:07 ns2 named[13165]: no IPv6 interfaces found Aug 31 15:54:07 ns2 named[13165]: listening on IPv4 interface lo, 127.0.0.1#53 Aug 31 15:54:07 ns2 named[13165]: listening on IPv4 interface eth0, 209.151.96.66#53 Aug 31 15:54:07 ns2 named[13165]: command channel listening on 127.0.0.1#953 Aug 31 15:54:07 ns2 named[13165]: couldn't open pid file 'named.pid': Permission denied Aug 31 15:54:07 ns2 named[13165]: exiting (due to early fatal error) Aug 31 15:54:07 ns2 named: named startup failed Aug 31 16:08:17 ns2 named: failed Aug 31 16:08:20 ns2 named: failed Aug 31 16:08:20 ns2 named: /etc/rndc.key:24: 'options' redefined near 'options' Aug 31 16:11:25 ns2 named: failed Aug 31 16:11:27 ns2 named[13250]: starting BIND 9.2.4 -u named -t /var/named/chroot Aug 31 16:11:27 ns2 named[13250]: using 2 CPUs Aug 31 16:11:27 ns2 named[13250]: loading configuration from '/etc/named.conf' Aug 31 16:11:27 ns2 named[13250]: no IPv6 interfaces found Aug 31 16:11:27 ns2 named[13250]: listening on IPv4 interface lo, 127.0.0.1#53 Aug 31 16:11:27 ns2 named[13250]: listening on IPv4 interface eth0, 209.151.96.66#53 Aug 31 16:11:27 ns2 named[13250]: command channel listening on 127.0.0.1#953 Aug 31 16:11:27 ns2 named[13250]: couldn't open pid file 'named.pid': Permission denied Aug 31 16:11:27 ns2 named[13250]: exiting (due to early fatal error) Aug 31 16:11:27 ns2 named: named startup failed Aug 31 16:27:49 ns2 named[13329]: starting BIND 9.2.4 -u named -t /var/named/chroot Aug 31 16:27:49 ns2 named[13329]: using 2 CPUs Aug 31 16:27:49 ns2 named[13329]: loading configuration from '/etc/named.conf' Aug 31 16:27:49 ns2 named[13329]: no IPv6 interfaces found Aug 31 16:27:49 ns2 named[13329]: listening on IPv4 interface lo, 127.0.0.1#53 Aug 31 16:27:49 ns2 named[13329]: listening on IPv4 interface eth0, 209.151.96.66#53 Aug 31 16:27:49 ns2 named[13329]: /etc/rndc.key:1: configuring key 'rndckey': bad base64 encoding Aug 31 16:27:49 ns2 named[13329]: loading configuration: bad base64 encoding Aug 31 16:27:49 ns2 named[13329]: exiting (due to fatal error) Aug 31 16:27:49 ns2 named: named startup failed Aug 31 16:31:42 ns2 named[13361]: starting BIND 9.2.4 -u named -t /var/named/chroot Aug 31 16:31:42 ns2 named[13361]: using 2 CPUs Aug 31 16:31:42 ns2 named[13361]: loading configuration from '/etc/named.conf' Aug 31 16:31:42 ns2 named[13361]: no IPv6 interfaces found Aug 31 16:31:42 ns2 named[13361]: listening on IPv4 interface lo, 127.0.0.1#53 Aug 31 16:31:42 ns2 named[13361]: listening on IPv4 interface eth0, 209.151.96.66#53 Aug 31 16:31:42 ns2 named[13361]: command channel listening on 127.0.0.1#953 Aug 31 16:31:42 ns2 named[13361]: couldn't open pid file 'named.pid': Permission denied Aug 31 16:31:42 ns2 named[13361]: exiting (due to early fatal error) Aug 31 16:31:42 ns2 named: named startup failed Aug 31 16:45:28 ns2 named[13403]: starting BIND 9.2.4 -u named -t /var/named/chroot Aug 31 16:45:28 ns2 named[13403]: using 2 CPUs Aug 31 16:45:28 ns2 named[13403]: loading configuration from '/etc/named.conf' Aug 31 16:45:28 ns2 named[13403]: no IPv6 interfaces found Aug 31 16:45:28 ns2 named[13403]: listening on IPv4 interface lo, 127.0.0.1#53 Aug 31 16:45:28 ns2 named[13403]: listening on IPv4 interface eth0, 209.151.96.66#53 Aug 31 16:45:28 ns2 named[13403]: command channel listening on 127.0.0.1#953 Aug 31 16:45:38 ns2 named[13403]: running Aug 31 16:45:38 ns2 named: named startup succeeded _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
