All the details I have so far are here:
https://bugzilla.redhat.com/show_bug.cgi?id=1127415
Here's the general pain though. logrotate-3.8.7-1.fc20.i686 behaves just fine for me
in a regular Fedora 20 install:
# /etc/cron.daily/logrotate ; echo $?
0
However, on all my recent Fedora 20 live spins:
# /etc/cron.daily/logrotate ; echo $?
error: error renaming temp state file /var/lib/logrotate.status.tmp
0
If I tell logrotate to use a different state file, even in the same directory, it works
fine. I suspect this is rather telling:
# lsof /var/lib/logrotate.status*
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd-j 423 root mem REG 0,34 8388608 15250
/var/log/journal/2150106cce5d48d883d7253aa337cacd/system.journal
systemd-j 423 root 26u REG 0,34 8388608 15250
/var/log/journal/2150106cce5d48d883d7253aa337cacd/system.journal
dhclient 823 root 5w REG 0,34 519 15707
/var/lib/dhclient/dhclient--eth0.lease
journalct 1003 root mem REG 0,34 8388608 15250
/var/log/journal/2150106cce5d48d883d7253aa337cacd/system.journal
journalct 1003 root 5r REG 0,34 8388608 15250
/var/log/journal/2150106cce5d48d883d7253aa337cacd/system.journal
Since I only see the problem with the live spin and a regular install doesn't show
this file open by any processes I thought I'd ask around here if anyone has ideas. It
seems very odd that these processes would have this file open.
--
John Florian