Bug 781675 - logrotate does not rotate catalina.out due to permission problems
Summary: logrotate does not rotate catalina.out due to permission problems
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: tomcat6
Version: 17
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: David Knox
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-14 06:30 UTC by Andreas Girgensohn
Modified: 2015-11-02 00:16 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-31 23:52:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Andreas Girgensohn 2012-01-14 06:30:40 UTC
Description of problem:

Logrotate produces the following error.

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):

tomcat6-6.0.32-17.fc16.noarch
logrotate-3.8.0-3.fc16.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Have the daily logrotate cron job run
2. Read the error message in email
  
Actual results:

Log doesn't get rotated.

Expected results:

Rotate the log

Additional info:

When adding "    su tomcat tomcat" to /etc/logrotate.d/tomcat6, the error goes away.

Bug 772591, bug 768355, and others report the same problem for other packages.

Comment 1 Ian Pilcher 2012-09-09 14:48:37 UTC
Still present in Fedora 17.

Comment 2 Mikolaj Izdebski 2013-03-14 14:38:36 UTC
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

Comment 3 joshua 2013-03-14 22:06:06 UTC
What does Fedora 19 have to do with this Fedora 17 issue?  The fact that the package won't be around in the future doesn't mean it isn't broken now, in a perfectly valid and currently maintained Fedora release.

Comment 4 Mikolaj Izdebski 2013-03-15 16:56:54 UTC
(In reply to comment #3)
> What does Fedora 19 have to do with this Fedora 17 issue?  The fact that the
> package won't be around in the future doesn't mean it isn't broken now, in a
> perfectly valid and currently maintained Fedora release.

This bug was closed by mistake. My intent was to close bugs reported against Fedora 19 and later only.

Comment 5 Fedora End Of Life 2013-07-03 22:11:11 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 17'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.

Comment 6 Fedora End Of Life 2013-07-31 23:52:46 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.