job stuck in 'starting up', not actually assigned at all

[LaszloSebo]

This task has been stuck in ‘starting up’ phase on a machine for more than an hour, despite the fact that it hasnt actually ever been rendering that frame (according to the logs):

The job ID is:
541717a70294981ba4f5a519

I only found one frame from that job in this slave’s log:

2014-09-15 11:33:52: 0: Plugin rendering frame(s): 1064

Required a manual requeue, the housecleaning never noticed this issue.
deadlineslave-LAPRO1364-2014-09-15-0000.zip (836 KB)

[rrussell]

Hmm… I wonder if during the dequeue process, there was an error that caused the task to get stuck in this state, in which case it could be possible that the slave just moved on to try and get the next task. Regardless though, housecleaning should detect this, so we’ve logged an issue to make sure that housecleaning will handle tasks that are stuck in the Waiting to Start state.

Cheers,
Ryan