+++ This bug was initially created as a clone of Bug #790334 +++ Description of problem: Tomcat's logrotate.d file needs to set "su root tomcat" to suppress logrotate errors like: error: skipping "/var/log/tomcat6/catalina.out" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Install tomcat 2. Run /etc/cron.daily/logrotate Actual results: Expected results: No errors. Additional info: Patch to fix is: diff --git a/tomcat-7.0.logrotate b/tomcat-7.0.logrotate index a87b4c0..926928a 100644 --- a/tomcat-7.0.logrotate +++ b/tomcat-7.0.logrotate @@ -4,5 +4,6 @@ rotate 52 compress missingok + su root tomcat create 0644 tomcat tomcat } --- Additional comment from Ivan Afonichev on 2012-02-14 11:23:31 CET --- Maybe it's better to set tomcat:root as owner for /var/log/tomcat ? --- Additional comment from Fedora Update System on 2012-02-22 21:05:28 CET --- tomcat-7.0.26-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/tomcat-7.0.26-1.fc16 --- Additional comment from Fedora Update System on 2012-02-22 21:05:45 CET --- tomcat-7.0.26-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/tomcat-7.0.26-1.fc17 --- Additional comment from Fedora Update System on 2012-02-23 03:23:57 CET --- Package tomcat-7.0.26-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing tomcat-7.0.26-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-2217/tomcat-7.0.26-1.fc16 then log in and leave karma (feedback). --- Additional comment from Fedora Update System on 2012-03-06 20:40:14 CET --- tomcat-7.0.26-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. --- Additional comment from Fedora Update System on 2012-03-16 22:22:07 CET --- tomcat-7.0.26-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
We would like to see the same errata released for tomcat6, both in Fedora 16 and Fedora 17 -- there is the same problem there because the log directory /var/log/tomcat6 has the same permissions. Thank you, Jan
Hmmm, bugs 748913, 781675, and 827039 all describe the same issue. Is there a plan to have the package respun with the fix?
Package tomcat6 has been deprecated in Fedora 19 and later. I am closing this bug as WONTFIX. For more information why tomcat6 was deprecated see: http://bugzilla.redhat.com/918010 http://lists.fedoraproject.org/pipermail/devel/2013-March/179847.html http://fedorahosted.org/fesco/ticket/1094
Reopening to address f18. The fix will be in tomcat6-6.0.36-2.fc18
tomcat6-6.0.36-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/tomcat6-6.0.36-2.fc18
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bugzilla is currently in MODIFIED state wince March, with update listed for Fedora 18. What is the current official status?
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days