Sometime, idle slave are shutting-down and repository (or pulse) doesn’t see that they are offline.
Pulse always try to shut them down, but never see that they are not online anymore.
Sometime he see that deadline slave is not responding and generate a STALLED SLAVE REPORT, any many time not.
So I need to mark slave as offline to able Pulse to wake-up slave again.
Maybe it’s a network issue, but haven’t got any problem when shutting-down machine manually. (using monitor Shutdown Machine command)
This is a known issue that can happen on occasion, and we’re looking at ways to address it in Deadline 6.
Basically, a slave is given 30 seconds to clean up what it’s doing and then it’s closed forcefully. When it is killed like this, it is unable to set its state to Offline. This is done on purpose though so if the slave was in the middle of a task, Deadline will see the slave has stalled and then requeue its task so another slave can pick it up.
We’re hoping we can make this shutdown process a bit “smarter” so that the slave is only killed when it is actually “stuck”, as opposed to just taking a long time to clean up what it’s doing.
Cheers,
-Ryan
It s a very annoying issue… It happens every time the renderfarm is empty, and I got 10% slave doing nothing. 
So I need to control farm every day. I’m the only one able to mark slave as offline.
Any clue to reduce this issue ??? 
(a pulse setting, repository…)
Please !!! 
Best regards.
Hmm, this shouldn’t be a widespread issue…
The next time this happens, go to the actual slave machine and open the Deadline logs folder (%PROGRAMDATA%\thinkbox\deadline\logs) and grab the slave log. It should be the most recent slave log, unless you’ve launched the slave again. We can see what the slave is doing when this happens, and hopefully come up with some ideas.
Thanks!
