** Bug watch added: Debian Bug tracker #871592 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592
** Also affects: logrotate (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 Importance: Unknown Status: Unknown ** Description changed: - - Install logrotate + [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 you will get something like this "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate + - 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 - logrotate never recovers if the statefile is corrupted unless you remove - it or fix the corruption by hand. + [Regression Potential] - System will eventually run out of disk space and crash. + * 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 ** Description changed: [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) + * 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 -- 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: In Progress Status in logrotate source package in Trusty: New Status in logrotate source package in Xenial: New Status in logrotate source package in Zesty: New Status in logrotate source package in Artful: In Progress Status in logrotate package in Debian: Unknown Bug description: [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 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 : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
