log files are generating under bin directory
search cancel

log files are generating under bin directory


Article ID: 187955


Updated On:


CA Workload Automation DE - Business Agents (dSeries) CA Workload Automation DE DSERIES- SERVER CA Workload Automation DE - System Agent (dSeries) CA Workload Automation DE - Scheduler (dSeries)


We recently installed R12.2 application on as part of upgrade activity. We are noticing the log files(including tracelog, clilogs etc.) are getting generated 

under  --/opt/CA/WorkloadAutomation/bin OR /opt/CA/WorkloadAutomation 

instead of -- /opt/CA/WorkloadAutomation/logs

Logs are generated randomly under one of the above directories.

We did not update the value for any of the log locations after the installation was completed. Install was successful with no errors. Attached is the server installation directory. This behavior has been observed in multiple R12.2 environments so far. 


Release : 12.2



This issue is fixed after DE 12.2, see Workload Automation DE 12.2 Release Notes for details;
Log files
Log files getting created in the Server install directory or bin folder. Problem - 338
If the log file's (tracelogs.timestamp.txt) size becomes greater than the size you have specified, for the same timestamp, two files get created in the <install-directory>/logs folder. For example, tracelogs.timestamp_1.txt and tracelogs.timestamp_2.txt. Due to an issue, the second file was getting created in the <install-directory>/bin folder. This issue is now resolved.

Please open a case with Support if you need further assistance.