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:
RPM installs logrotate script in /etc/logrotate.d/syslog
This requests a rotation of /var/log/cron
logrotate gives error messages if the file does not exist.
Version-Release number of selected component (if applicable):
rsyslog-7.4.7-7.el7_0
How reproducible:
Always (unless something else creates /var/log/cron)
Steps to Reproduce:
1. Install RPM
2. /usr/sbin/logrotate /etc/logrotate.d/syslog
Actual results:
error: stat of /var/log/cron failed: No such file or directory
Expected results:
No message - i.e. success
Additional info:
The postinstall scriptlet ensures these files exist:
/var/log/{messages,secure,maillog,spooler}
Adding cron to that list should resolve this.
Shane, this should already be fixed with the bug 1144465. It seems you're not using the latest packages. Could you please check again with the latest version?
Tomas, you are correct, this is addressed in 7.4.7-12.
The resolution is to use "missingok" in the rotatelog file, which is robust.
With that fix in place there is no need for the postinstall scriptlet to create the files at all. I think removing that code would be A Good Thing.
(In reply to Shane Voss from comment #3)
> With that fix in place there is no need for the postinstall scriptlet to
> create the files at all. I think removing that code would be A Good Thing.
I agree that would likely be a good simplification. OTOH, that scriptlet enforces a certain umask on the files. Removing it now would change the behavior.
The code needs rethinking but preferably in Fedora.
(In reply to Tomas Heinrich from comment #4)
> Removing it now would change the behavior.
> The code needs rethinking but preferably in Fedora.
Fair enough. I am happy with things as they are - thanks!
Description of problem: RPM installs logrotate script in /etc/logrotate.d/syslog This requests a rotation of /var/log/cron logrotate gives error messages if the file does not exist. Version-Release number of selected component (if applicable): rsyslog-7.4.7-7.el7_0 How reproducible: Always (unless something else creates /var/log/cron) Steps to Reproduce: 1. Install RPM 2. /usr/sbin/logrotate /etc/logrotate.d/syslog Actual results: error: stat of /var/log/cron failed: No such file or directory Expected results: No message - i.e. success Additional info: The postinstall scriptlet ensures these files exist: /var/log/{messages,secure,maillog,spooler} Adding cron to that list should resolve this.