Why does removing these files help resolve issues when SAS VA (SAS 9.4) goes down

[Mahis]

Hello everyone,

I want to know why, when SAS VA of SAS 9.4 goes down, the following classical methods help resolve the problem? What is the role of these specific files?

a) Stop SAS services on mid tier server :

./sas.servers stop

Check if no SAS process remain and kill it (ps -ef | grep sas)

b) clean up following elements (replace <SASConfig> by your current SAS configuration directory of course) :

rm -rf <SASConfig>/Lev1/Web/WebAppServer/SASServer*_1/temp/*
rm -rf <SASConfig>/Lev1/Web/WebAppServer/SASServer*_1/work/Catalina/localhost/*
rm -rf <SASConfig>/Lev1/Web/WebAppServer/SASServer*_1/logs/tmlog*.*
rm -rf <SASConfig>/Lev1/Web/WebAppServer/SASServer*_1/logs/*.epoch
rm -rf <SASConfig>/Lev1/Web/activemq/data/*

c) Start SAS services :

./sas.servers start

Could someone explain the role of these specific files and why these steps are necessary?

Thank you.

[Kurt_Bremser · Accepted solution]

These are temporary (utility) and log files written by the web application server (tomcat); once you run out of space there, the server stops working.

Set up a strategy for regularly cleaning up / archiving those files, and run such a process from the scheduler.

[Mahis]

Thank you so much.