Red Hat Bugzilla – Bug 1257745
/etc/logrotate.d/tomcat tries rotating catalina.out instead of catalina.YYYY-MM-DD.log
Last modified: 2015-11-01 19:19:37 EST
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?
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.
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?
Thanks but this doesn't help me nor help me how to fix the issue with starting/stopping Tomcat with Systemd.