Version

Argent Job Scheduler all versions

Date

Friday, 7 October 2016

Summary

Sometimes a Job in the Argent Job Scheduler never end and show status as ‘Running’ in console screen (J1 screen) even though the Job Log states the Job has ended

Technical Background

Argent Job scheduler considers a Job as ended only when all the processes spawned by the Job and all of its child processes have ended

If any process or child process is left running even after the completion of the task, Job Scheduler Console screen (screen J1) will have the status of the Job as ‘Running’, even though the Job Log states that the Job has ended with Exit code displayed

Typically this is a programming error in the main, mother Job

To debug such incidents where the Job status remains in ‘Running’ status, change the Debug Level of the Queue Engine to ‘LOG_HIGHLY_DETAILED’

Please visit the following link and look for the section ‘\Logs’ to know more about log debug level settings:

https://help.argent.com/argent-job-scheduling/argent-scheduler/directory-structure/argent-queue-engine-home-directory/argent-queue-engine-home-directory/

Execute the Job in question and review the Job’s Job Log when the task has actually completed

In ideal case, the Job log should contain lines mentioning ‘Start’ Event and ‘Exit’ Event for all those process and child processes spawned by the Job along with their PIDs

Sample lines mentioning the Start and Exit of a process are given below

Search the log files to find ‘exited’ Event for all those PIDs that have a ‘started’ Event

If any PID is missing an ‘exited’ Event, search for the same PID in the Task Manager screen of the Queue Engine to confirm the process is still running

Resolution

N/A