06-29-2018 08:49 PM
I'm crawling data which is approximately 7 GB in size. Then, i'm surprised that my C:\ drive storage is being full. Then i checked, i found my TOMCAT-server.log file is exceeding 140 GB. How could it be effecting log file? is it because my crawling activity or anyother reason of it? And is there any solution for bringing back my storage volume? i'm trying to open the log file on notepad and notepad++ but it can't because the size is too large.
4 weeks ago
Is your tomcat log log4j configured as DEBUG?
I am wondering if you can stop tomcat, delete/backup existing big tomcat log file, and then restart tomcat. Try to monitor the new log file and see what is getting recoreded in the log.
2 weeks ago
the only way to reset the log file is to stop the ERDAS Apollo Tomcat service and delete the file. You can configure the logging behaviour in this file:
c:\Program Files\Hexagon\ERDAS APOLLO\webapps\erdas-apollo\WEB-INF\classes\log4j.properties
Per default each day a new logfile is created. You can reduce the log threshold changing the line
If you don't want a new log file every day you can use the RollingFileAppender instead of the DailyRollingFileAppender
log4j.appender.file=org.apache.log4j.RollingFileAppender log4j.appender.file.file=C:/Program Files/Hexagon/ERDAS APOLLO/log/TOMCAT-server.log log4j.appender.file.MaxFileSize=20MBlog4j.appender.file.MaxBackupIndex=10 log4j.appender.file.layout=org.apache.log4j.PatternLayout log4j.appender.file.layout.ConversionPattern=%d %-5p (%t)[%c] %m%n log4j.appender.file.Threshold=INFO
With this configuration a new log file is created if it is greater than 20MB. And only 10 of these log files are hold in your system, older log files are deleted by the logging framework.