Bug 1223569 - Logs in catalina.out are lost with each RPM update
Summary: Logs in catalina.out are lost with each RPM update
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: tomcat
Version: 21
Hardware: All
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Ivan Afonichev
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-20 22:00 UTC by Doug Knight
Modified: 2015-12-02 18:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 12:40:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Doug Knight 2015-05-20 22:00:56 UTC
Description of problem:
The rpm for tomcat contains /var/log/tomcat/catalina.out in its manifest.  Each time the tomcat package is updated, rpm replaces the catalina.out log with the mostly-empty file from the package.  All logs in catalina.out are lost in the process.

Version-Release number of selected component (if applicable):
All versions since commit 3cb34c71 (tomcat-6.0.32-1)

How reproducible:
Always

Steps to Reproduce:
1. Install an old version of tomcat
2. Create logs in /var/log/tomcat/catalina.out
3. yum upgrade tomcat

Actual results:
catalina.out is clobbered, and the logs are lost.

Expected results:
Not this.

Additional info:

I recommend dropping catalina.out from the manifest.  Since it is a log file, and should initially be empty, we don't want rpm to manage its contents.  Likewise, we don't care about tracking its metadata since we are using the /var/log/tomcat directory to control access to the tomcat log files.

I am not sure why we are putting the "tomcat-X.Y.Z RPM installed" message in catalina.out; it seems like something that belongs in a system log, not an application log.  If we really need to keep that message around, we should add it with something like
runuser -s /bin/bash -c '/bin/echo "%{name}-%{major_version}.%{minor_version}.%{micro_version} RPM installed" >> %{logdir}/catalina.out'
from the %post script.

Comment 1 Fedora End Of Life 2015-11-04 11:53:06 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora  'version'
of '21'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 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 this bug is closed as described in the policy above.

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 2 Fedora End Of Life 2015-12-02 12:40:11 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.


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