Timeline for Logrotate: "log does not need rotating" why?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 17, 2019 at 21:45 | comment | added | Mark | On CentOS, I modified /var/lib/logrotate.status to get logrotate working. As indicated by EightBitTony, the daily logrotate will remembers the history. Unless the file is in the history already with a date in the past, logrotate won't rotate the file. | |
| Oct 25, 2017 at 12:52 | comment | added | Centimane |
To add to this, editing the date in the status file to be older than the rotation policy is enough to convince logrotate it needs to rotate the log when it runs again.
|
|
| Apr 24, 2015 at 13:12 | comment | added | Fluffy |
-d + -f makes logrotate report "needs rotating" for all files, even the ones that don't match
|
|
| Oct 6, 2014 at 21:22 | comment | added | JGurtz | Also check for possible use of the -s argument in the invocation for status file location | |
| Nov 29, 2011 at 10:07 | comment | added | kaleissin | In FreeBSD it's /var/run/logrotate.status | |
| Jun 24, 2011 at 11:59 | vote | accept | Rich | ||
| Jun 24, 2011 at 8:14 | history | answered | EightBitTony | CC BY-SA 3.0 |