Certain job_list job not running; batch queue gummed up

• Article Type: General
• Product: Aleph
• Product Version: 20

Problem Symptoms:
The xxx50 job_list job cir-32 is released and shows in jobd.log as being released, but, despite the fact that the xxx50 batch queue (lib_batch) is running, the job sits (as seen in util c/7) in the queue -- and other jobs which should run back up behind it.

If the job is deleted via util c/8, the other jobs then run.

Cause:
Problem with the time on the server. (It was found that, while the times shown in the $alephe_scratch job log are correct, the timestamp of the log entry seen in "ls -lrt" is incorrect.)

Resolution:
Correct the time on the server. See below.