Logrotate no longer works..."Too Many Open Files"

Matthew Saltzman mjs at CLEMSON.EDU
Wed Jun 27 13:14:04 UTC 2007


On Wed, 2007-06-27 at 08:48 -0400, Mike Burger wrote:
> Saturday morning, I ran a yum update on my FC5 server.  I believe one of the
> packages updated in that run was logrotate.
> 
> Ever since then, the logrotate job, in /etc/cron.daily, has problems, yielding
> this output:
> 
> /etc/cron.daily/logrotate:
> 
> error: error running postrotate script for /var/named/chroot/var/log/named/* 
> error: error running postrotate script for /var/named/chroot/var/log/named/* 
> error: error running postrotate script for /var/named/chroot/var/log/named/* 
> error: error running postrotate script for /var/named/chroot/var/log/named/* 
> error: error creating output file /var/named/chroot/var/log/named/update.log.1.3.2:
> Too many open files
> ....
> error: error running postrotate script for /var/named/chroot/var/log/named/* 
> error: error opening /var/log/samba/inmrdmb6535lt01.log: Too many open files
> error: error opening /var/log/samba/laurie.log: Too many open files
> error: error opening /var/log/samba/nmbd.log: Too many open files
> error: error opening /var/log/samba/smbd.log: Too many open files
> error: error opening /var/log/squid/access.log: Too many open files
> error: error opening /var/log/squid/cache.log: Too many open files
> error: error opening /var/log/squid/store.log: Too many open files
> error: error running postrotate script for /var/log/squid/store.log 
> error: error creating output file /var/log/messages: Too many open files
> error: error creating output file /var/log/secure: Too many open files
> error: error creating output file /var/log/maillog: Too many open files
> error: error creating output file /var/log/spooler: Too many open files
> error: error creating output file /var/log/boot.log: Too many open files
> error: error creating output file /var/log/cron: Too many open files
> error: error running postrotate script for /var/log/messages /var/log/secure
> /var/log/maillog /var/log/spooler /var/log/boot.log /var/log/cron 
> error: error creating state file /var/lib/logrotate.status: Too many open files
> 
> The "postrotate script" for named is "/sbin/service named reload", for squid
> it's "/usr/sbin/squid -k rotate", etc.  It doesn't seem to matter, though,
> what the postrotate script is...it fails to run, regardless, meaning that
> I now wind up with a lot of "service.log.1", "service.log.2", etc, but no
> "service.log"
>  
> I'm also very confused about the "Too many open files" piece, as I'm not having
> anything else give me problems with an error of that nature.
> 
> Any ideas?

What do you see if you ls -lR in /var/log
and /var/named/chroot/var/log/?

Check the logrotate specs to  see if there are any that define the files
to be rotated using wildcards.  If you find one, file a bug with that
package.

> 
> 




More information about the fedora-list mailing list