Closed hjoliver closed 2 months ago
Closed by https://github.com/cylc/cylc-doc/pull/638?
If not, push a commit onto upstream/troubleshotting
.
I didn't think it was covered very well, but maybe I didn't look closely enough. I'll re-check and tweak it if necessary...
Here's the troubleshooting entry for job status not updating:
OK cool, that's good enough. I'll close this.
Add to the new troubleshooting section once #638 is merged.
The Cylc UIs show the scheduler's current knowledge of task and job state. For active tasks, that involves interaction with the external world:
(Note the above assumes TCP job status messaging; otherwise the scheduler periodically polls for job status).
Tasks may get "stuck" in an incorrect state if anything blocks this external job status information. For instance, you may see a task that stays in the "submitted" state even though it actually ran and completed.
Polling the task - by which the scheduler queries the job runner and checks the
job.status
file - will return the correct result, but you may still need to determine what went wrong.Incorrect task status implies one of two things:
You can determine what happened by examining the job logs:
job.status
log regardless of message sendjob.err
log will record errors (this will not stop the job from completing, however)job.status
file does not record completion, and the job is no longer present in the job runner queue, then the job must have been hard-killed