When manually shutting down a slave via eg. teamviewer it shows as “idle” in the monitor and after 15 minutes orso it is switched to “stalled”
Tried it with multiple machines, always happens here unless it is shut down remotely through deadline (only then it shows “offline”)
today I have one slave that has been shutdown by deadline and shows at “after last task complete” “shut down machine” for 11 minutes before it switched to “stalled”
It sounds like the slave isn’t writing its Offline state to the database while it is shutting down. We can’t reproduce this here, so we’ll need some more information.
-
The next time this happens, can you get the slave log from the session where this occurred and post it? You can find the logs folder from the Launcher menu by selecting Explore Log Folder.
-
Which operating system is the slave running on?
-
When you say you’re shutting it down via teamviewer, are you just closing the slave from the user interface (ie: the File menu or the [X] button)?
Thanks!
Ryan
Here the slave log:
2014-07-25 20:48:07: BEGIN - 3DNODE5\node5
2014-07-25 20:48:07: Deadline Launcher 7.0 [v7.0.0.25 R (79978a431)]
2014-07-25 20:48:07: Launching Slave:
2014-07-25 20:48:07: Launcher Thread - Launcher thread initializing...
2014-07-25 20:48:07: Updating Repository options
2014-07-25 20:48:07: - Remote Administration: enabled
2014-07-25 20:48:07: - Automatic Updates: disabled
2014-07-25 20:48:07: Launcher Thread - Remote administration is enabled
2014-07-25 20:48:07: Launcher Thread - Launcher thread listening on port 17070
2014-07-25 20:48:17: Auto Configuration: Picking configuration based on: 3DNode5 / 192.168.0.15
2014-07-25 20:48:17: Auto Configuration: No auto configuration could be detected, using local configuration
2014-07-25 20:48:17: Updating Repository options
2014-07-25 20:48:17: - Remote Administration: enabled
2014-07-25 20:48:17: - Automatic Updates: disabled
2014-07-25 20:53:17: Auto Configuration: Picking configuration based on: 3DNode5 / 192.168.0.15
2014-07-25 20:53:17: Auto Configuration: No auto configuration could be detected, using local configuration
2014-07-25 20:53:17: Updating Repository options
2014-07-25 20:53:17: - Remote Administration: enabled
2014-07-25 20:53:17: - Automatic Updates: disabled
2014-07-25 20:57:55: fe80::9471:af37:f67c:3564%11 has connected
2014-07-25 20:57:55: Launcher Thread - Received command: OnLastTaskComplete ShutdownMachineIdle : : 3DNode5
2014-07-25 20:57:55: Sending command to slave: OnLastTaskComplete ShutdownMachineIdle :
2014-07-25 20:57:55: Got reply: 3DNODE5: Sent "OnLastTaskComplete ShutdownMachineIdle : " command. Result: ""
2014-07-25 20:57:55: Launcher Thread - OnLastTaskComplete: Set to ShutdownMachineIdle
2014-07-25 20:57:55: Launcher Thread - Responded with: Success|
2014-07-25 20:57:58: Launcher Thread - OnLastTaskComplete: Checking if all slaves have shutdown
what I did:
- start machine via deadline (remote control)
- login via teamviewer
- push the windows start button and select shutdown
- the computer shuts down, shows idle state until the stalled time-out** is reached and get stalled.
the remote machine is running win 7 64bits.
did this many times with DL6 and was never a problem.
I also see it doesn’t get an auto-configuration… could that why it doesn’t map the drives?
**
I notice when I change the wait times in the repository Slave settings that it seem to be minimum values, is that correct?
I tried to set the Stalled waiting time to 2 minutes, but that doesn’t seem possible. It seems that 5 is the lowest value to stay sticky.
(same goes for the Thermal shutdown, minimum being 600).
perhaps good to give a pop-up and mention the minimum value?
Ah, you’re shutting down the machine, not just the slave application. Thanks for clarifying this. We’ve logged this as an issue and we’ll see if we can reproduce it.
Thanks!
Ryan