Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

For some reason logrotate is rotating logs daily instead of weekly, even though all the config files for logrotate seem to be set to weekly. Any ideas?



test -x /usr/sbin/logrotate || exit 0
/usr/sbin/logrotate /etc/logrotate.conf


# see "man logrotate" for details
# rotate log files weekly

# keep 4 weeks worth of backlogs
rotate 4

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

# uncomment this if you want your log files compressed

# packages drop log rotation information into this directory
include /etc/logrotate.d

# no packages own wtmp, or btmp -- we'll rotate them here
/var/log/wtmp {
    create 0664 root utmp
    rotate 1

/var/log/btmp {
    create 0660 root utmp
    rotate 1

# system-specific logs may be configured here


/var/log/apache2/*.log {
        rotate 52
        create 640 root adm
                if [ -f "`. /etc/apache2/envvars ; echo ${APACHE_PID_FILE:-/var/run/}`" ]; then
                        /etc/init.d/apache2 reload > /dev/null
share|improve this question
I'm having the exact same problem, were you able to solve it? – Daniel Ristic Apr 19 at 15:39

Notice this line in /etc/logrorate.conf:

include /etc/logrotate.d

Perhaps you have some stale or backup files lying around in that directory, which get included, and specify daily rotation?

As a workaround, and if you still can't figure it out, and if you only ever want to have your files rotated weekly, then you can change the frequency with which logrotate is executed through cron, thus changing the precision of log rotation from daily to weekly.

share|improve this answer
The program-specific logrotate files in /etc/logrotate.d are actually what I want to run, my particular interest in this case being the Apache logrotate config file I posted above. There is only one apache file in that directory. No forgotten backups. Also, I'm trying to avoid using cron.weekly for this, as the impression I get is that that violates best practices. – steve.t.sullian Mar 26 '13 at 17:06

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.