[Bug 1709670] [NEW] logrotate never recovers if the statefile is corrupted
Launchpad Bug Tracker
1709670 at bugs.launchpad.net
Wed Aug 9 18:18:53 UTC 2017
You have been subscribed to a public bug by Eric Desrochers (slashd):
[Impact]
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.
[Test Case]
- 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 run logrotate
Unless you remove the statefile and start again or fix the corruption by
hand.
[Regression Potential]
* 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)
[Other Info]
* Upstream commit:
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a
* Upstream bug:
https://github.com/logrotate/logrotate/issues/45
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592
** Affects: logrotate (Ubuntu)
Importance: Medium
Assignee: Eric Desrochers (slashd)
Status: In Progress
** Affects: logrotate (Ubuntu Trusty)
Importance: Undecided
Status: New
** Affects: logrotate (Ubuntu Xenial)
Importance: Undecided
Status: New
** Affects: logrotate (Ubuntu Zesty)
Importance: Undecided
Status: New
** Affects: logrotate (Ubuntu Artful)
Importance: Medium
Assignee: Eric Desrochers (slashd)
Status: In Progress
** Affects: logrotate (Debian)
Importance: Unknown
Status: Unknown
** Tags: patch sts sts-sru-needed
--
logrotate never recovers if the statefile is corrupted
https://bugs.launchpad.net/bugs/1709670
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.
More information about the Ubuntu-sponsors
mailing list