Idle slaves Dequeuing Task

Deadline
1

We suddenly have a problem with blades getting stuck as Idle. (Windows Server 2008, 3dsMax 2014 & vray job)
The current example is a job submitted at priority 100:
Current job status is 601 frames, 33 rendering, 267 queued, 300 completed.
Server park status is 55 total, 33 rendering, 14 idle etc…

I’ve manually logged in and started the deadline slave on one of the idle blades and it stops without any errors at Dequeuing Task and just stops there. It get the task name listed for a while, then it blanks out all those fields after a few minutes.
I restarted the slaves and machines, and the repository service, but still the same blades are getting stuck on the idle status.

Two of the render blades rendered one frame each after I manually restarted the Deadline service, but after that they got stuck in the Idle status again.
Deadline 6.0.0.51561 with Pulse running.

Got any advice? I’m kind of puzzled by this since there don’t seem to be any logs containing any useful information.

2

Looks like it got solved with a workaround…

I submitted a small batch of the unfinished frames as a new job and gave it the highest priority (old job 99, new 100).
Restarted the slave on the idle blades and they started rendering the new job without problem. After the small job completed and they continued rendering on the original job afterwards.

So far everything looks good

3

That is really odd, but glad to see it got working for you. If you see that happen again, can you turn on verbose slave logging in repository options, then send over a log file when it happens a bit? Thanks.