Hi Brandon,
I've been investigating this same issue as well.
The logs in JIRA's Installation directory are the Tomcat log files, which are not rotated/expired automatically.
The logs in JIRA's Home directory are the Atlassian log files, which are rotated at around 20MB.
My catalina.out log file (in the Installation log directory) at one point was up to 8GB in size. Other log files here weren't as large but dated back years.
Following these links:
I was able to come-up with a log rotation/expiration solution that works:
(Note: The path to your installation directory and log4j.properties may be different than mine)
- I edited the <tt>/usr/local/atlassian/jira/atlassian-jira/WEB-INF/classes/log4j.properties</tt> file and removed console logging from the various logging categories:
sed -i 's/, console,/,/g' log4j.properties
- This got rid of the majority of logging from <tt>/usr/local/atlassian/jira/logs/catalina.out</tt>
- But there is still some logging when tomcat processes start in catalina.out so I need to rotate/expire this log file. We can use logrotate for this - here is the config I used in /etc/logrotate.d/atlassian:
/usr/local/atlassian/jira/logs/catalina.out {
copytruncate
dateext
monthly
rotate 6
compress
delaycompress
missingok
}
- I'm not sure if you're using Confluence as well. If so, you'll want to set-up log rotation for its catalina.out file as well. I didn't have to modify its log4j.properties file to remove console logging though.
- Next you'll want to come up with a scheme for expiring all of the other Tomcat log files. I wrote a script for that runs as a cron job nightly that removes files after they reach an age of my choosing. I'm happy to provide my script to you if you necessary.
Hope this helps get you going in the right direction. Le me know if you have questions.
-- Stephen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.