AutoSys Agent Disk Usage – Cleanup of Stranded output/error Logs in autosyslog Folder

[RAMESH INAGANTI]

Hi Team,

Is there any parameter we can configure to automatically clean up stranded output and error logs for AutoSys jobs in the autosyslog folder? We are experiencing increased disk utilization on the agent side, particularly on the D: drive where the autosyslog folder is located.

[Arihara Subramanian]

Hi Ramesh

Check below link for more information.

Clean Spool and Job Log Files

[RAMESH INAGANTI]

Hi Ari ,

The below parameters already enabled. not sure why too much job logs stored in autosyslog folder

oscomponent.joblog.success.autocleanup=true agent.spool.success.autocleanup=truerunnerplugin.spool.clean.enable=true

[Arihara Subramanian]

Try to below parameter with specific days which will keep only 7 days log and delete old logs.

runnerplugin.spool.expire=7d

[RAMESH INAGANTI]

Hi Ari,

hi Ari, The below parameter also already there 

runnerplugin.spool.expire=7d

[Michael Woods]

Hi Ramesh,

The STDXXX files are not considered 'Agent' logs and therefore are not targets for cleanup.  If space is an issue, here are some thoughts on how it can be managed to reduce it.

First, are you creating unique output files for each run or appending output to the existing output?  That will definitely keep growing.  

If the only the last run is important, you could use a specific name for each job and overwrite it for each job run.

Second, if you need to maintain the output for each run for some period of time, then I would suggest have a standard location for the output files.

For long term storage requirements, you could zip/tar up the directories contents and move them to another location on a regular basis.

For short term requreiments, you could use a 'find' command to locate the files older than X and delete them.

Hope that helps,

Mike