Comment 1 for bug 1709670

Using the above reproducer ^ ....

I confirm that logrotate never recover if the statefile is corrupted unless you remove it or fix the corruption by hand.

The upstream fix introduce in 3.12.0-18 [1] is fixing the issue[2] (tested using Artful so far)

Since all supported|devel releases are lower than 3.12 [3], then all releases are affected.

[1] - https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a

# git describe --contains b9d8200
3.12.0~18

[2] - https://github.com/logrotate/logrotate/issues/45

[3] - rmadison
logrotate | 3.8.7-1ubuntu1 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el
logrotate | 3.8.7-1ubuntu1 | vivid | source, amd64, arm64, armhf, i386, powerpc, ppc64el
logrotate | 3.8.7-1ubuntu1.1 | trusty-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el
logrotate | 3.8.7-2ubuntu2 | xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
logrotate | 3.8.7-2ubuntu2.16.04.1 | xenial-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
logrotate | 3.8.7-2ubuntu3 | zesty | source, amd64, arm64, armhf, i386, ppc64el, s390x
logrotate | 3.8.7-2ubuntu3 | artful | source, amd64, arm64, armhf, i386, ppc64el, s390x

Regards,
Eric