If I stop a slave it will stop and dequeue the current task it’s rendering but the slave won’t go to ‘offline’. If I then send a “start” command the “Time running” stat will reset to a couple seconds and start working.
Also I think there should be two levels of slave status. There should be “offline” and there should be “stopped”. That way I can tell if the launcher is running but not the slave. It seems like the launcher could be a good proxy for whether a slave is powered up or not.
Can you post the log after the slave shuts down? We’ll take a look to see if there were any errors updating its state.
Currently, the slave is the only app that updates the slave state. The launcher doesn’t update it, so it can’t indicate if the machine itself is still online. We had a “ping” option in v5 and earlier that would show if the slave’s machine was online. We should probably look at adding the ping option back into Deadline 6.
Cheers,
Ping always timed out for me. Which is why I thought maybe the launcher status update would be more reliable.
Still doesn’t update DB. Stopping a slave through remote control leaves slaves status frozen as “rendering”. Even if remote command status is “Succeeded”.
We haven’t looked into this yet. It’s still logged as bug, so we’ll get to it soon!