WCC-Autosys Log Files during Batch Job Run Time

[vinothini G]

Hi Team,

Greetings..!

we have a bash script .sh which creates a .log files in server in folder(opt/CA/log) during run time...
and we use Elastic Batch Platform for Batch job Run.(example sample job runs every 30 minutes)
during run time.the .log files are created in server with incorrect data as "job terminated" rather than "job success" only for some runs..
other 30 minutes runs(same job)..job logs are updating correctly in server.
this issue appears occasionaly over other different jobs during the Batch runs..

pls share your thoughts on what cauisng the incorrect .log file update in server

[Reginold DAlmeida]

Hi Vinothini,

We need more description of our environment. Since you mentioned it as a  Elastic Batch Platform, A simple answer would be the server/node running your script might be scaling down or up  based on the demand and your bash script might be capturing the termination signals. Autosys might recognize the node died and automatically retry the job on a new node where it succeeds.

[Siva Kumar Somaraju]

Additionally you may check the script logic to locate where "job terminated" is defined in the .sh file. Identify if any specific command is failing or causing the script to generate this message in the log.

 

Review the std_err_file and std_out_file defined in the job configuration to catch any other messages and verify if explicit exit codes are defined in the script. Coordinate with the Application Team / Script Owner to investigate the script's failure logic and logs for those specific runs.