How to make the jira-xxx-stdout.xxx.log file roll over

[Dave]

The stdout and stderr log files can become huge (some instances in the GBytes).

Platform: Winsdows Server 2008 R2

Jira: any version 4.x upwards, running as a service

You can change the location of the log files (https://confluence.atlassian.com/display/JIRA/How+to+change+the+location+of+stdout+and+stderr+logs)

How an I make them roll over after x size and x files?

there are options to change the atlassian-jira.log file to a rolling file appender (https://confluence.atlassian.com/display/JIRA/Logging+and+Profiling)

But not indication how to affect the jira stdout log file.

[Andy Brook [Plugin People] · Accepted solution]

According to https://confluence.atlassian.com/display/JIRA/Running+JIRA+as+a+Service the logs should rotate daily. If thats not the case, I dont know. Support call ?

[Dave]

Probably have to be a support call because they definately do not rotate. We have a file that is around 2GB in size

[Dave]

Actually having looked into this further. The link you provide simply states that the Windows service manages teh riotation on a daily basis. I cannot find any evidence of this.

The following Jira ticket (https://jira.atlassian.com/browse/JRA-8841) raised in 2005 and updated this year indicates also that the stydout logs do not rotate and teh answer in that case was to stop Jira logging to teh console.

[Andy Brook [Plugin People]]

Disabling the console log would seem sensible, if you can see the same content in the File log (which may inherit better rolling?).