![\"52afc1a25a054_avaya_button[1]\"](\"http:\/\/pariswells.com\/blog\/wp-content\/uploads\/2015\/01\/52afc1a25a054_avaya_button1-150x150.png\")
I was asked to investigate a server which was using lots of disk and CPU useage every 5 minutes. I logged in and check perf mon to find out tomcat7.exe was zipping up all the files in \\onexportal\\Tomcat\\Server\\logs into from *RollingFiles. After running this , all I could see in the logs is<\/p>\r\n
“couldn’t be deleted after adding to zip”<\/p>\r\n
A quick research of TomCat turns out the Avaya server was using the log4j Apache Logging Service ( http:\/\/logging.apache.org\/log4j\/2.x\/ )<\/p>\r\n
The config for this was in Tomcat\\Server\\bin\\log4j.xml<\/p>\r\n
After checking there was a parameter in there called <param value=”10MB” name=”MaxFileSize”\/> which meant it would try to Roll these constantly.<\/p>\r\n
You can change <param value=”true” name=”Append”\/> to <param value=”false” name=”Append”\/> and restart the service which means the logs will start from scratch everytime you restart the “Avaya one-X Portal for IP Office” service<\/p>\r\n
or you can clear the logs file by using a sheuduled script<\/p>\r\n","protected":false},"excerpt":{"rendered":"
I was asked to investigate a server which was using lots of disk and CPU useage every 5 minutes. I logged in and check perf mon to […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[889,888,891,892,894,890,893],"class_list":["post-1434","post","type-post","status-publish","format-standard","hentry","category-random","tag-avaaya","tag-couldnt-be-deleted-after-adding-to-zip","tag-high-cpu","tag-high-iops","tag-log4j","tag-onex","tag-tomcat7-exe"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t