Logrotate hangs

tangle · 06-20-2005, 02:35 PM

I have a Slackware 10.0 box that hangs when logrotate runs. I ran it with the script in /etc/cron.daily and when I ran it manually.

Here is the output when I run logrotate -v /etc/logrotate.conf

Code:

root@holmesnet:~# logrotate -v /etc/logrotate.conf
reading config file /etc/logrotate.conf
including /etc/logrotate.d
reading config file syslog
reading config info for /var/log/cron /var/log/debug /var/log/maillog /var/log/messages /var/log/secure /var/log/spooler /var/log/syslog
reading config info for /var/log/wtmp

I reinstalled the Slackware package and still the same thing. I looked thru the log files and did not see any messages. So you could say that I am stumped. Any help would be appericated.

peter_robb · 06-21-2005, 06:39 AM

What copy options are in those files?
Try again with the copytruncate option in each..

tangle · 06-21-2005, 11:15 AM

It is running the default for Slackware.

/etc/logrotate.d/syslog

Code:

/var/log/cron /var/log/debug /var/log/maillog /var/log/messages /var/log/secure /var/log/spooler /var/log/syslog {
    sharedscripts
    postrotate
        /bin/kill -HUP `cat /var/run/syslogd.pid 2>/dev/null` 2>/dev/null || true
    endscript
}

/etc/logrotate.conf

Code:

# /etc/logrotate.conf
#
# logrotate is designed to ease administration of systems that generate large
# numbers of log files.  It allows automatic rotation, compression, removal, and
# mailing of log files.  Each log file may be handled daily, weekly, monthly, or
# when it grows too large.
#
# logrotate is normally run daily from root's crontab.
#
# For more details, see "man logrotate".

# rotate log files weekly:
weekly

# keep 4 weeks worth of backlogs:
rotate 4

# create new (empty) log files after rotating old ones:
create

# uncomment this if you want your log files compressed:
#compress

# some packages install log rotation information in this directory:
include /etc/logrotate.d

# Rotate /var/log/wtmp:
/var/log/wtmp {
    monthly
    create 0664 root utmp
    rotate 1
}

# Note that /var/log/lastlog is not rotated.  This is intentional, and it should
# not be.  The lastlog file is a database, and is also a sparse file that takes
# up much less space on the drive than it appears.

# system-specific logs may be also be configured below:

peter_robb · 06-21-2005, 04:53 PM

I suggest changing the "create" option to "copytruncate"

This eliminates any possible conflict if a file is open for writing when logrotate wants to work on it.

The hanging could be a damaged binary file or a write/read conflict.
These kind of possibilities need to be eliminated one by one if there aren't any logfile messages to describe the problem.

tangle · 06-22-2005, 02:34 PM

I changed the create option and it still hung. Since the PC is not that important , I'll go ahead and re-install. Thanks for the help.