On Wed, 17 Jun 2015 11:44:02 +1200 Alex King <a...@king.net.nz> wrote: > I suspect the message will be from a configuration which includes the > compress option without. delaycompress.
There is no need to guess, you can run logrotate with the --verbose setting and find out which log it was processing before the error occured. A good way to do this is to modify the logrotate cron to add --verbose and sit and wait for the logs to reach your inbox. Rich > > cd /etc/logrotate.d > (grep -L delaycompress *;grep -l compress *)|sort |uniq -c|awk > '/^\s*2/{print $2}' > > On my system this produces: > > apt > aptitude > munin-node > samba > > I suspect in my case munin-node is the culprit, but I haven't yet tested > that. > > But it should be possible to add delaycompress to some or all of the > files to identify the source of the errors. > > Thanks, > Alex > >