logrotate failure

[David G. Miller]

Gene Heskett <gene.heskett at verizon.net> wrote:

> And they both do.  When I ran it like Rick recommended, 
> (logrotate -vf ./logrotate.conf) from the logrotate.d directory, then the 
> real error popped out, and that was because there wasn't a user 'named' 
> because bind wasn't installed.  It is now and although bind isn't 
> configured or running, logrorate, at least from the cli, now works.  I 
> even copied my old version of the logrotate.d/syslog from FC2 because it 
> has all my additions in it, and it now Just Works(TM) from the cli at any 
> rate.
>
> To me thats a packageing error, there shouldn't be a file in logrotate.d 
> for named UNTIL bind has been installed.
>
> I guess most folks weren't bit because they do install bind.  I generally 
> use host files here.
Gene, by any chance was this box upgraded from a previous release?  I 
don't have a named user on my box that got a clean install of FC6:

# cat /etc/passwd | grep named

nor do I have bind installed:

# rpm -qa | grep bind
bind-libs-9.3.3-6.fc6
ypbind-1.19-5
bind-utils-9.3.3-6.fc6

and logrotate works just fine. 

You might want to check to see if you still have a bind logrotate file 
in /etc/logrotate.d.  It makes sure the rotated logs still have 
named:named as the owner and group which would cause the problem your 
seeing.  The files in logrotate.d are placed there by each application 
that wants to have its logs rotated.  All logrotate does is run the 
files.  It's possible an upgrade that removed bind didn't remove 
/etc/logrotate.d/named.

Cheers,
Dave

-- 
Politics, n. Strife of interests masquerading as a contest of principles.
-- Ambrose Bierce