Status: Closed (View Workflow)
I understand that there are limitations to logging based on log4j and in Tomcat but it is a pain for an Administrator, and for Atlassian support engineers to work with massive logfiles.
After some time catalina.out can grow significantly (50+ GB) and system can run out of space. Also at Windows it's not possible to log-rotate catalina.out without stopping JAVA due to platform restriction.
Either ship Jira with a logging system which has log rotation enabled by default for catalina.out
- Or reduce logging for catalina.out implemented, see
JRASERVER-67796for more details
- catalina.out is a file attached to STDOUT and STDERR of the JAVA process.
- Snippet from catalina.sh
- at the same time, _catalina.XXXX-YY-ZZ.log _files generated and controlled by Tomcat itself. Those files are log-rotated by Tomcat.
- Jira has internal Logrotate (log4j and juli) for everything it can control as Java process. catalina.out is outside the Java process.
Choose one them:
- Options to rotate the catalina.out and detailed steps for using logrotate are documented at How to Rotate the Catalina Log File.
- For Windows see separate KB: How to rotate the tomcat catalina log file on windows
- Increase logging level for console loggers to WARN and restart JIRA, see diff:
- Remove all console from log specific logging events, see examples