Red Hat Bugzilla – Bug 218388
Logrotate should rotate logs even if there are some errors on the configuration
Last modified: 2015-01-07 19:15:17 EST
I think this is a "me too".
We had a rpm install of snort, where we later reconfigured it so that it didn't
write logfiles under /var/log/snort/*/* - as refered to in it's logrotate.d file.
However, when logrotate runs, it can't find any subdirs under /var/log/snort (as
we had deleted them), AND IT EXITED - CEASING TO RUN OTHER logrotate FILES!!
We found out a week later when the huge (un-rotated) squid logfiles crashed
i.e if you have a logrotate config file that refers to files in directories that
don't exist, logrotate exits, not running any remaining logrotate jobs. I don't
know if this is an exact match for this ticket - but I assume so?
I think there should be no such dependencies. The status of one logrotate config
file should not impact any others. Isn't that the point of RPMs - keep things
nice and separate?
It seems to be too late for 4.6, moving to 4.7.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.