(OO) Support Tip: OO does not clean up localhost_access_log.yyyy-mm-dd logs
On a daily basis, OO creates a new localhost_access_log.yyyy-mm-dd log file. Unlike other log files (such as the wrapper_log), OO does not have a mechanism to clean them up so left to itself OO will cause its own failure by running the Centrals out of disk space. How to resolve?
This logging feature is handled by a third party library in Tomcat. This third party library supports only switching from daily to hourly logging. This means you will only have the logging data for the past 24 hours. After that, it is rolled.
Per Engineering, in order for us to fix this in the code we need to replace the logging library. It turns out that the replacement cannot be done as part of a hotfix due to potential regressions and hopefully will be handled in a future version.
Option 1 - Based on Tomcat documentation (http://tomcat.apache.org/tomcat-5.5-doc/config/valve.html#Access Log Valve) , it seems that it’s only possible to manage the rotation either to hourly, daily or monthly by adding the fileDateFormat parameter in the server.xml file located at \central\tomcat\conf\server.xml.
Option 2 - Archive older files into a backup directory and/or delete them. Additionally, write an OO flow and schedule it.
Defect QCCR8C25447 Logfiles consum fast the available disk space has been submitted for this issue.
Please see the knowledge document at https://softwaresupport.hpe.com/km/KM02739039