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.
Bug 1257745 - /etc/logrotate.d/tomcat tries rotating catalina.out instead of catalina.YYYY-MM-DD.log
Summary: /etc/logrotate.d/tomcat tries rotating catalina.out instead of catalina.YYYY-...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tomcat
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: David Knox
QA Contact: tomcat-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-27 20:15 UTC by Yoshifumi Kinoshita
Modified: 2019-08-15 05:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-08 21:47:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 2 moraj 2015-09-03 16:49:45 UTC
I reported this behavior to Red Hat. I need some direction for an application I am setting up. What is the expected behavior for Tomcat? 

Should it be creating the log as catalina.out or as catalina.[YYYY.MM.DD].log?


The Logrotated conf file on RHEL 7.1 points to a catalina.out, but Tomcat is creating a catalina.[YYYY.MM.DD].log and it appears the log gets created each Tomcat is started.

Tomcat 6 on RHEL 6 created a catalina.out and Logrotated pointed to that file name. Was this feature deprecated in Tomcat 7 on RHEL 7?

Comment 3 Yoshifumi Kinoshita 2015-09-08 21:47:58 UTC
I found when we use /usr/sbin/tomcat to start tomcat, logs are written to catalina.out as well. So this is not a bug.

Comment 4 moraj 2015-09-09 02:36:48 UTC
I thought the Systemd was the preferred method for stopping and starting service on RHEL 7 not scripts/binaries found in /usr/sbin. When I use Systemd to stop and start Tomcat, Tomcat does not create a catalina.out as you have stated.

I have seen this issue on both CenOS 7 and RHEL 7.  

What is the preferred method for stopping the free/public version of Tomcat, /usr/sbin/tomcat or Systemd?

Comment 5 moraj 2015-09-09 02:38:56 UTC
Thanks but this doesn't help me nor help me how to fix the issue with starting/stopping Tomcat with Systemd.


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