We recently upgraded from v11.2 to v12.3, and are having a problem with Unix jobs that we run with job type 'Command'. We have many jobs set up like this and they were running fine on v11.2 but on v12.3 even though the job log shows that it finished successfully, the job ends up with at status of 'ENDED_VANISHED'. The jobs do not fail every time, and when they do fail, we can restart the job and it finishes successfully.
If we change the job type to 'Shell Script' and rework our commands to run that way, we don't seem to have this problem. However, this would affect a large number of jobs and we do not want to make the changes unless absolutely necessary. Is there something we may have missed in our configuration to take care of this?
Here's a link to the documentation where it describes these two job types:
https://docs.automic.com/documentation/webhelp/english/AA/12.3/DOCU/12.3/Automic%20Automation%20Guides/help.htm#AWA/Objects/obj_job_UNIX.htm?Highlight=unix%20job
We see this in the unix agent log:
MAIN-THREAD 20191119/133356.354 start_job <-- (terminated normally, Result (pid): '50754')
MAIN-THREAD 20191119/133356.354 process_aktj: result of function start_job()-call : 50754
MAIN-THREAD 20191119/133356.354 process_aktj: job was started with fork() call!
MAIN-THREAD 20191119/133356.354 CheckPidJEntry(search pid 50754) -->
MAIN-THREAD 20191119/133356.354 CheckPidJEntry <-- (terminated normally, entry unavailable)
MAIN-THREAD 20191119/133356.354 process_aktj: job-entry with process ID '50754' was not found!
------------------------------
Cloud Engineer
------------------------------