[BlueOnyx:11503] Re: 5196R Oct 5 2012 bind update issues
Chris Gebhardt - VIRTBIZ Internet
cobaltfacts at virtbiz.com
Mon Oct 8 12:04:13 -05 2012
Hey Gerald!
Gerald Waugh wrote:
> [root at ns2 ~]# cat /var/log/yum.log | grep bind | grep "Oct 05"
> Oct 05 07:32:09 Updated: 30:bind-libs-9.3.6-20.P1.el5_8.4.i386
> Oct 05 07:32:18 Updated: 30:bind-9.3.6-20.P1.el5_8.4.i386
> Oct 05 07:32:20 Updated: 30:bind-utils-9.3.6-20.P1.el5_8.4.i386
> Oct 05 07:32:25 Updated: 30:bind-chroot-9.3.6-20.P1.el5_8.4.i386
> Oct 05 07:32:41 Updated: 30:bind-chroot-9.3.6-20.P1.el5_8.4.i386
>
> Errors started on Oct 8, Odd that many of the db.domain.tld were updated
> on Oct 8
> there are 133 domain records and 84 were updated on Oct 8, the others
> were updated Oct 5
>
> Since the update seeing these errors in logwatch for all 133 domains
> (133 lines in logwatch)
>
> zone domain1.ltd/IN: refresh: could not set file modification time of
> 'db.domain1.tld': permission denied: 9 Time(s)
> zone domain2.tld/IN: refresh: could not set file modification time of
> 'db.domain2.tld': permission denied: 9 Time(s)
At first I thought I was left out and you were testing the super-secret
new 5196R. Then I shifted my fingers around on the keyboard and figure
you're probably on 5107R in this case. I'll go with that, since it
suits my ego better.
While I don't have a 5107R build here, I do have some 5106R and 5108R
systems.
I had a look at 5108R:
Sep 18 06:00:39 Updated: 32:bind-libs-9.8.2-0.10.rc1.el6_3.3.x86_64
Sep 18 06:00:45 Updated: 32:bind-9.8.2-0.10.rc1.el6_3.3.x86_64
Sep 18 06:00:46 Updated: 32:bind-chroot-9.8.2-0.10.rc1.el6_3.3.x86_64
Sep 18 06:00:47 Updated: 32:bind-utils-9.8.2-0.10.rc1.el6_3.3.x86_64
Well 5108R is on 9.8.2-0.10, and 5107R should be using the same
versions, just on the 32-bit libraries instead, right?
So I next looked at 5106R:
Oct 02 09:32:16 Updated: 30:bind-libs-9.3.6-20.P1.el5_8.4.i386
Oct 02 09:32:47 Updated: 30:bind-9.3.6-20.P1.el5_8.4.i386
Oct 02 09:32:58 Updated: 30:bind-utils-9.3.6-20.P1.el5_8.4.i386
Oct 02 09:33:18 Updated: 30:bind-chroot-9.3.6-20.P1.el5_8.4.i386
Oct 02 09:34:52 Updated: 30:bind-chroot-9.3.6-20.P1.el5_8.4.i386
That seems more appropriate for what you're finding. I then did this:
# grep "could not set file" /var/log/messages
But I got no results (not on my 5106R or 5108R that I looked at.
What does your ownership look like for /etc/named ? It should be
root:named. Maybe that's the problem?
--
Chris Gebhardt
VIRTBIZ Internet Services
Access, Web Hosting, Colocation, Dedicated
www.virtbiz.com | toll-free (866) 4 VIRTBIZ
More information about the Blueonyx
mailing list