As I reported initially, logrotate finally tries to remove a file, which
does not exist due to option delaycompress.
Adding a clause for a particular logfile with option nodelaycompress causes
a matching file to exist and logrotate removes it indeed :(
Relevant part of /etc/logrotate.conf
#-----------------------------------
dateext
size 2M
delaycompress
missingok
tabooext + .orig
create
compress
include /etc/logrotate.d
/var/log/iptables-eth.log {
size 6M
nodelaycompress
}
bash script "simulating" what logrotate does regarding to iptables-eth.log
#-------------------------------------------------------------------------
cd /var/log
mv iptables-eth.log{,-20080827}
touch iptables-eth.log
gzip -9 iptables-eth.log-20080827
rm iptables-eth.log-20080827.gz
Hopefully everyone hit by this bug has backups to restore the data eaten
by logrotate, as I luckily had :)
Conclusions
#----------
(1) Please retitle bugreport to "dataloss in case of config options
dateext size nodelaycompress".
(2) Please raise severity at least to important.
(3) We learn: Whenever logrotate config files have been modified, a backup
of our logfiles prior to next logrotate run is advisable.
--
Roland Eggner
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
