Interruptible flag and jobs not rendering?

Deadline
1

Hello,

We just recently did a test sending a series of low priority renders using the interruptible flag. The idea obviously being that more important jobs would trump them throughout the day. When I came in this morning there were a series of tasks falsely reporting that they were rendering but the farm was completely empty. I re-queued all the tasks and now everything is rendering.

Are other people using this option? We mainly render stills with the tasks being tile renders.

Thanks,

-Rob

2

Hey Rob,

The interruptible flag shouldn’t be causing any problems like this…

Which version of Deadline are you using?

Cheers,

  • Ryan
3

Deadline Version: 5.1.0.46114

4

Thanks! We did fix a bug in 5.1.46398 that would cause the slave to throw errors if the job it was working on was interruptible and was then deleted. It could be possible the issue you’re seeing (assuming it’s directly related to using the interruptible flag) could be related to the bad code that we fixed when dealing with the original problem.

Before I recommend updating though, it would be handy to see a log from a slave that was “rendering” one of those tasks when it really wasn’t. It might be difficult to figure out which slaves/logs to check now that the tasks have been requeued, so you will probably have to try and reproduce the problem again for us to collect more info.

If it does happen again, note the slave that is shown “rendering” a task, and then go to that machine and select Help -> Explore Log Folder from the Slave UI. Sort on modified date so that the most recent logs are at the top, and then grab the last 5 SLAVE logs (not monitor or launcher logs), zip them up, and post them. Also, let us know the task ID and job ID that it belongs to so that we can find the job in the logs. We can then use this info to find where the slave lost track of the task, and hopefully why.

Cheers,

  • Ryan