Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
If a log file entry is inadvertently duplicated among config files in /etc/logrotate.d , logrotate fails (doesn't rotate any log files), but still returns zero return code, so there's no notification of the issue. This leads to log files not getting rotated, growing to fill the filesystem.
/etc/cron.daily/logrotate specifically looks for a non-zero return code from the logrotate command it runs in order to alert about an issue. Because a config duplication error returns 0, no alert is logged.
# /usr/sbin/logrotate -s /var/lib/logrotate/logrotate.status /etc/logrotate.conf
error: syslog:1 duplicate log entry for /var/log/boot.log
# echo $?
0
#
Version-Release number of selected component (if applicable):
logrotate-3.8.6-17.el7.x86_64
How reproducible:
Always, when a duplicate log file entry is present. Main issue is if duplicate entry is in /etc/logrotate.d/syslog (and there is already another, separate config file for that logfile), files in the syslog config file don't get rolled.
Steps to Reproduce:
if /etc/logrotate.d/bootlog exists and looks like :
/var/log/boot.log
{
missingok
daily
copytruncate
rotate 7
notifempty
}
And your /etc/logrotate.d/syslog looks like this :
/var/log/boot.log
{
missingok
daily
copytruncate
rotate 7
notifempty
}
You will get the "error: syslog:1 duplicate log entry for /var/log/boot.log" and none of the additional files listed in /etc/logrotate.d/syslog will get rotated. And because it returns 0, /etc/cron.daily/logrotate won't log the error.
Actual results:
# /usr/sbin/logrotate -s /var/lib/logrotate/logrotate.status /etc/logrotate.conf
error: syslog:1 duplicate log entry for /var/log/boot.log
# echo $?
0
#
Expected results:
# /usr/sbin/logrotate -s /var/lib/logrotate/logrotate.status /etc/logrotate.conf
error: syslog:1 duplicate log entry for /var/log/boot.log
# echo $?
1
#
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:1024
Description of problem: If a log file entry is inadvertently duplicated among config files in /etc/logrotate.d , logrotate fails (doesn't rotate any log files), but still returns zero return code, so there's no notification of the issue. This leads to log files not getting rotated, growing to fill the filesystem. /etc/cron.daily/logrotate specifically looks for a non-zero return code from the logrotate command it runs in order to alert about an issue. Because a config duplication error returns 0, no alert is logged. # /usr/sbin/logrotate -s /var/lib/logrotate/logrotate.status /etc/logrotate.conf error: syslog:1 duplicate log entry for /var/log/boot.log # echo $? 0 # Version-Release number of selected component (if applicable): logrotate-3.8.6-17.el7.x86_64 How reproducible: Always, when a duplicate log file entry is present. Main issue is if duplicate entry is in /etc/logrotate.d/syslog (and there is already another, separate config file for that logfile), files in the syslog config file don't get rolled. Steps to Reproduce: if /etc/logrotate.d/bootlog exists and looks like : /var/log/boot.log { missingok daily copytruncate rotate 7 notifempty } And your /etc/logrotate.d/syslog looks like this : /var/log/boot.log { missingok daily copytruncate rotate 7 notifempty } You will get the "error: syslog:1 duplicate log entry for /var/log/boot.log" and none of the additional files listed in /etc/logrotate.d/syslog will get rotated. And because it returns 0, /etc/cron.daily/logrotate won't log the error. Actual results: # /usr/sbin/logrotate -s /var/lib/logrotate/logrotate.status /etc/logrotate.conf error: syslog:1 duplicate log entry for /var/log/boot.log # echo $? 0 # Expected results: # /usr/sbin/logrotate -s /var/lib/logrotate/logrotate.status /etc/logrotate.conf error: syslog:1 duplicate log entry for /var/log/boot.log # echo $? 1 #