Yes, you need to run logrotate more than once a day to achieve this. This is answered in the seconds paragraph of the man page logrotate(8): Normally, logrotate is run as a daily cron job. It will not modify a log multiple times in one day unless the criterion for that log is based on … Read more
In the postrotate, I redirect both stderr and stdout to a log file to see what happens: postrotate /usr/bin/mysqladmin flush-logs > /var/log/mysqladmin.flush-logs 2>&1 endscript What I get is: /usr/bin/mysqladmin: connect to server at ‘localhost’ failed error: ‘Access denied for user ‘root’@’localhost’ (using password: NO)’ It sounds like mysqladmin doesn’t read /root/.my.cnf during logrotate. So, try … Read more
You should be able to call an external script in the postrotate directive: postrotate /path/to/your.sh endscript and have that script do the moving, e.g.: #!/bin/bash newdir=/var/log/example/`date +%Y%m%d` mkdir $newdir mv /var/log/example.1.gz $newdir find /var/log/example -mindepth 1 -maxdepth 1 -mtime +7 \ -type d -print0 | xargs -0 rm -rf However, it might be easier to … Read more
It seems that if I just change the logrotate script to be a single block, i.e. /var/log/apache2/*.log, /srv/apache/logs/*.log {….} I don’t get the segfault. So it was just the two blocks were causing a second restart attempt during the first restart… If I enter apache2ctl graceful & apache2ctl graceful & apache2ctl graceful & apache2ctl graceful … Read more
Adding delaycompress to the configuration section for /var/log/messages solved the problem. From man logrotate: delaycompress Postpone compression of the previous log file to the next rota‐ tion cycle. This only has effect when used in combination with compress. It can be used when some program cannot be told to close its logfile and thus might … Read more
1) My logrotate on my older Hardy install is identical to Mike’s answer 2) Looking at the /etc/crontab file, cron.daily is run at 6:25am on my install 3) If the pre-rotate commands are assigned to a a pattern, and the log files match that pattern, then yes
I’m not aware of any variables you can use if that’s what you’re looking for. However immediately after rotating the log, you should know precisely the name that the file has been rotated to based on the configuration you’ve set for the rotation (/var/log/somefile.1 or the like). Perhaps it would be easier to answer if … Read more
You don’t tell logrotate which file to rotate on the command line. You pass it a configuration file. So in your case, logrotate is reading /var/log/syslog and trying to parse it as a config file and failing (hence your errors). If you want to rotate /var/log/syslog it needs to be listed in a logrotate config … Read more
The most elegant answer is to put thatonespecial.log in a separate directory so it wouldn’t be able to match the wildcard. If that won’t work, then you can use globs to narrow down your wildcard. It’s messy, but if you absolutely can’t move the file location then it’s probably your only real option. Something like … Read more
In that case you may want to use postrotate. In the example below postrotate will delete files that are older that 1 day after logs been rotated, feel free to modify it to fit your needs. /opt/log/app/app.log.* { missingok nomail postrotate /usr/bin/find /opt/log/app/ -name “app.log.*” -type f -mtime +0 -exec rm {} \; endscript }