** Description changed:
logrotate never recovers if the statefile is corrupted unless you remove it
or fix the corruption by hand.
System will eventually run out of disk space on /var/log for instance.
- Install logrotate
- Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate
the statefile "var/lib/logrotate/status"
- Modify "/var/lib/logrotate/status" by removing the first line in order to
corrupt the file
- Re-run "/etc/cron.daily/logrotate" and one will get the following error :
"error: bad top line in state file /var/lib/logrotate/status" every time you
Unless you remove the statefile and start again or fix the corruption by
- * Risk of potential regression is low, and couldn' be worst than the actual
situation where logrotate doesn't recover from a corrupt statefile.
- The current patch does recover (after verification)
+ * Risk of potential regression is low, and IMHO couldn't be worst than the
actual situation where logrotate simply doesn't recover from a corrupt
+ * The current patch does recover (after verification) and has been through
some upstream CI validation, community feedbacks, et al.
* Upstream commit:
* Upstream bug:
* Debian bug:
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
logrotate never recovers if the statefile is corrupted
To manage notifications about this bug go to:
ubuntu-bugs mailing list