http://bugzilla.novell.com/show_bug.cgi?id=559867 http://bugzilla.novell.com/show_bug.cgi?id=559867#c2 --- Comment #2 from Ken Yap 2009-12-02 14:41:57 UTC --- I've also just seen the same symptoms of unresponsiveness and high CPU usage at another site, on both an i586 and an x86_64 machine. This site is using bind as an origin server, and doing full resolution, no forwarders, but is not accessible to the outside, so no views, and also no chance of a DoS attempt. Again, reverting to -18.7.1 removed the symptoms. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=559867 http://bugzilla.novell.com/show_bug.cgi?id=559867#c4 --- Comment #4 from Ken Yap 2009-12-03 08:45:27 UTC --- Ok, thanks, I have installed it on a non-critical server: # rpm -Fhv bind-9.5.2P1-0.1.x86_64.rpm bind-libs-9.5.2P1-0.1.x86_64.rpm bind-utils-9.5.2P1-0.1.x86_64.rpm bind-chrootenv-9.5.2P1-0.1.x86_64.rpm .. # rpm -qa bind* bind-9.5.2P1-0.1 bind-libs-9.5.2P1-0.1 bind-utils-9.5.2P1-0.1 bind-chrootenv-9.5.2P1-0.1 # rcnamed restart Shutting down name server BIND waiting for named to shut down (28s) done Starting name server BIND No obvious problems at startup, but I'll let it run for a while and report back. # ps ax | grep named 17829 ? Ssl 0:00 /usr/sbin/named -t /var/lib/named -u named -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=559867 http://bugzilla.novell.com/show_bug.cgi?id=559867#c6 --- Comment #6 from Ken Yap 2009-12-06 09:01:46 UTC --- Still looking good, working normally. 17829 ? Ssl 0:23 /usr/sbin/named -t /var/lib/named -u named -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=559867 http://bugzilla.novell.com/show_bug.cgi?id=559867#c8 --- Comment #8 from Ken Yap 2009-12-10 01:25:25 UTC --- Just an observation. Some of the bind packages, e.g. bind-libs, arrived later in the update repository, at least as far as my zypper was concerned. I noticed that bind-libs showed up later. Would installing an updated bind package without the corresponding bind-libs and maybe bind-chrootenv cause problems? I thought that dependencies would prevent me from mixing bind-18.8.1 with bind-libs-18.7.1, but perhaps not. That would explain why I was the only one with the problem, all the other people didn't update during this period when the latest bind was one patch version of the latest bind-libs. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=559867 http://bugzilla.novell.com/show_bug.cgi?id=559867#c10 --- Comment #10 from Ken Yap 2009-12-12 00:08:50 UTC --- Yes, it seems to work fine when all the components are updated at the same time. So far so good on various machines. Ironically I would not be in this situation if I had just let the automatic update take care of it but I thought that a bind update should be applied immediately but it seems that bind-libs did not get updated at the same time. Perhaps in future, the dependencies should be stated in the spec file to prevent mismatch of components. I guess you can close this ticket, it doesn't look like the problem will recur. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.