Public bug reported:
- 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 you will get something like this
"error: bad top line in state file /var/lib/logrotate/status" every time you
run logrotate
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 and crash.
** Affects: logrotate (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1709670
Title:
logrotate never recovers if the statefile is corrupted
Status in logrotate package in Ubuntu:
New
Bug description:
- 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 you will get something like this
"error: bad top line in state file /var/lib/logrotate/status" every time you
run logrotate
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 and crash.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
