Page MenuHomePhabricator

Logrotate fails for: "$FILE No such file or directory"
Open, LowPublic


Cron Daemon <>
7:25 AM (1 hour ago)

to root 
error: error opening /var/log/squid3/access.log.1.gz: No such file or directory
run-parts: /etc/cron.daily/logrotate exited with return code 1

In this case access.log.1.gz was present on disk and its content was bigger than zero bytes. I had to manually gzip it.

Event Timeline

elukey created this task.Dec 22 2016, 7:34 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 22 2016, 7:34 AM

Change 342586 had a related patch set uploaded (by Elukey):
[operations/puppet] Increase the squid's logrotate log retetion to 2

Change 342586 merged by Elukey:
[operations/puppet] Increase the squid's logrotate log retention to 2

jbond added a subscriber: jbond.EditedMar 13 2019, 2:41 PM

I had a variant of this during clinic

error: error creating output file /var/log/squid3/access.log.1.gz: File exists
run-parts: /etc/cron.daily/logrotate exited with return code 1

This is caused when logrotate has a problem between the compress and move stage. the logrotate action would be something like

rm /var/log/squid3/access.log.2.gz
gzip /var/log/squid3/access.log.1
mv  /var/log/squid3/access.log.1.gz  /var/log/squid3/access.log.2.gz
mv /var/log/squid3/access.log /var/log/squid3/access.log.1

if something happens between steps 2 and three then /var/log/squid3/access.log.1.gz gets left behind and the next time logrotate tries todo step 2 it fails