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 we have more locations to be rotated using the same definition - i.e:
/proj/intranet/css.s3group.com/logs/*log
/proj/intranet/wpad/logs/*log
/proj/intranet/x509.s3group.com/logs/*log
/var/log/httpd/*log {
    missingok
    notifempty
    sharedscripts
    delaycompress
    size 10M
    postrotate
        /bin/systemctl reload httpd.service > /dev/null 2>/dev/null || true
    endscript
}

and some directory above (say /proj/intranet/css.s3group.com/logs) has incorrect permissions (group writable), then logrotate fails to log files not only in /proj/intranet/css.s3group.com/logs, but in the other locations above, too.
 

Version-Release number of selected component (if applicable):
logrotate-3.8.6-17.el7.x86_64

How reproducible:
always

Actual results:
logrotate fails to rotate logs

Expected results:
logrotate refuses to rotate logs only in locations which are not valid (say invalid permissions), but continue to rotate logs in the other locations.

This is a known bug triggered by the `sharedscripts` directive.  It has not been fixed upstream yet.

*** This bug has been marked as a duplicate of bug 1320955 ***