I am also seing this on a 14.04 server using logrotate package version
3.8.7-1ubuntu1:

$ dpkg -l|grep logrotate
ii  logrotate                                              3.8.7-1ubuntu1       
                amd64        Log rotation utility

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.5 LTS
Release:        14.04
Codename:       trusty


Execution of logrotate from cron.daily aborts because of an existing file. Mail 
from cron below ("Filen eksisterer" is Danish for "File exists"):

/etc/cron.daily/logrotate:
error: error creating output file /var/log/syslog.1.gz: Filen eksisterer
run-parts: /etc/cron.daily/logrotate exited with return code 1

Looking at the syslog files there is both a syslog.1 and a syslog.1.gz
where the latter shouldn't exist because of delaycompress option. Also
the .gz is a compressed version of the plain file:

$ gunzip --stdout /var/log/syslog.1.gz | diff --report-identical-files - 
/var/log/syslog.1
Files - and /var/log/syslog.1 are identical


This suggests that logrotate was most likely interrupted after compressing 
syslog.1 to syslog.1.gz but before it was moved/rotated into syslog.2.gz. On 
subsequent executions this stale file causes logrotate to abort rotation 
entirely.


The issue has been addressed in recent upstream releases; 
https://github.com/logrotate/logrotate/pull/23

Also discussed in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=734688

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630516

Title:
  Logrotate fails repeatedly with /etc/cron.daily/logrotate: error:
  error creating output file /var/log/... File exists run-parts:
  /etc/cron.daily/logrotate exited with return code 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1630516/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to