SOI\tomcatI\temp\loglog* files are getting very large
Article ID: 132100
Updated On:
Products
CA Service Operations Insight (SOI)
Issue/Introduction
we checked that our disk increase too much and we discover that we have in the folder SOI\tomcatI\temp\loglog* files one of that 95gb.
in that file the most entrie that appear is
Fri Feb 15 10:47:38 GMT 2019 org.apache.log4j.helpers.LogLog[9] null ERROR log4j:ERROR Attempted to append to closed appender named [SAMDEBUG].
java.lang.Throwable
in that file the most entrie that appear is
Fri Feb 15 10:47:38 GMT 2019 org.apache.log4j.helpers.LogLog[9] null ERROR log4j:ERROR Attempted to append to closed appender named [SAMDEBUG].
java.lang.Throwable
Environment
SOI 4.2
Resolution
please open the file SOI\tomcat\lib\log4j.xml and comment the following section so it is not active anymore and restart the SOI services with
<root>
<!-- Capture all errors -->
<level value="ERROR" />
<appender-ref ref="SAM" />
<appender-ref ref="SAMDEBUG" />
</root>
SOI\tools\soitoolbox --stopAllServices and
SOI\tools\soitoolbox --startAllServices
<root>
<!-- Capture all errors -->
<level value="ERROR" />
<appender-ref ref="SAM" />
<appender-ref ref="SAMDEBUG" />
</root>
SOI\tools\soitoolbox --stopAllServices and
SOI\tools\soitoolbox --startAllServices
Feedback
Powered by
