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:
By default logrotation configuration for httpd uses delaycompress option as follows :
# cat /etc/logrotate.d/httpd
/var/log/httpd/*log {
missingok
notifempty
sharedscripts
delaycompress
postrotate
/bin/systemctl reload httpd.service > /dev/null 2>/dev/null || true
endscript
}
Customer is requesting to add comment as follows before delaycompress in /etc/logrotate.d/httpd for better user experience.
# The delaycompress only has effect when used in combination with compress option in default configuration /etc/logrotate.conf. Without compress in logrotate.conf delaycompress option is harmless and does nothing.
Version-Release number of selected component (if applicable):
httpd-2.4.6-89.el7_6.x86_64
How reproducible:
- Not clarified if delaycompress would work by default or need any configuration.
Steps to Reproduce:
1. Install httpd
2. Check if delaycompress is set in httpd logrotation configuration
3. Check if compress option is set in logrotation.conf global configuration.
Actual results:
- No mention of delaycompress dependency on compress
Expected results:
- Comment should mention that delaycompress is effective only with compress option.
Additional info:
In the logrotate man page it is mentioned very clearly that delaycompress only has effect
with "compress":
delaycompress
Postpone compression of the previous log file to the next rotation cycle. This only has effect when used in combination with compress. It can be
We are not planning to change the config file for current releases of Red Hat Enterprise Linux, but I have added a comment for future major releases:
https://src.fedoraproject.org/rpms/httpd/c/c99e83a2d8d3fb9808b1048f5f7d0550882f4521?branch=master
I understand that the "compress" option will not be added because doing so would change behaviour of existring installations.
However I would propose to remove the "delaycompress" option.
It is not functional without the compress option and the current configuration is confusing.
Thanks in advance.
The problem is that if "compress" is used *without* delaycompress for httpd, that will end up with correct/broken/dropped logs. Hence, delaycompress is used to get correct behaviour if "compress" is configured globally.
Description of problem: By default logrotation configuration for httpd uses delaycompress option as follows : # cat /etc/logrotate.d/httpd /var/log/httpd/*log { missingok notifempty sharedscripts delaycompress postrotate /bin/systemctl reload httpd.service > /dev/null 2>/dev/null || true endscript } Customer is requesting to add comment as follows before delaycompress in /etc/logrotate.d/httpd for better user experience. # The delaycompress only has effect when used in combination with compress option in default configuration /etc/logrotate.conf. Without compress in logrotate.conf delaycompress option is harmless and does nothing. Version-Release number of selected component (if applicable): httpd-2.4.6-89.el7_6.x86_64 How reproducible: - Not clarified if delaycompress would work by default or need any configuration. Steps to Reproduce: 1. Install httpd 2. Check if delaycompress is set in httpd logrotation configuration 3. Check if compress option is set in logrotation.conf global configuration. Actual results: - No mention of delaycompress dependency on compress Expected results: - Comment should mention that delaycompress is effective only with compress option. Additional info: