The 512 message means the job completed abnormally, and tidal has assigned it internal status of 512. Specifically that it ran and completed on its own, but it returned a status or exit code that was not 0. If the exact same job ID ran again, I would assume that it is scheduled to run multiple times a day using the same instance (instead of a new instance), or the job was rerun.
Thanks for the reply, so is there a way to determine why the job completed abnormally? The application team that runs the production jobs has put in a request to see if we can determine why the initial SFTP job did not complete. Is there another set of logs that I can look at that would provide more information to support the abnormal completion?
Well, we know the job completed abnormally because it had a non-zero exit code. What exit code that was can be found in the FTP logs if the agent is in high-debug. It'll be called "ftp.log"
To put an agent in high debug:
============================================================ Windows Agent: 1. Open the TIDAL Service Manager on the agent machine 2. Select the agent in the dropdown 3. Click on the dots [...] 4. In the Service tab, change the path to include the DEBUG option to read "DEBUG=HIGH" 5. Click OK to save changes 6. Restart the agent ============================================================= *nix Agent: 1. Go to the agent machine and go to the directory the agent is installed in 2. go to "Bin/" and edit "tagent.ini" 3. Under "[config]" put "ovb=tidaldebug" 4. Restart the agent ============================================================
Thanks for your suggestion. We see similar error if multiple jobs are trying to execute the shell script. In agent logs it shows exit code of process 112 and status changed to 512. Do we know how can we identify what causes it to be failed?