Remote commands not working after sleep

Deadline
1

We have just upgraded to Deadline 8.0.4.1 from Deadline 6 and are having issues with remote commands.

Remote commands and execute commands work perfectly until the machine sleeps and then wakes up. After waking, the machine does not receive any remote commands. They all time out. To get it working again I need to remote in, log off the machine and log back in again. We are also finding that Deadline Slave does not run when the machines are woken up.

i don’t really know where to start with this, any advice would be appreciated. :confused:

2

Hey Rob,

Can you send over a slave log from the slave from after the machine comes up from sleep? Would like to see both Launcher and Slave logs. Thanks.

3

Hi, is this good?

Launcher

2016-07-04 16:31:37: BEGIN - DELL-C6220-01\render 2016-07-04 16:31:37: Deadline Launcher 8.0 [v8.0.4.1 Release (49ce3656c)] 2016-07-04 16:31:37: Launcher Thread - Launcher thread initializing... 2016-07-04 16:31:37: Launcher Thread - Launcher thread listening on port 17080 2016-07-04 16:31:37: Local version file: C:\Program Files\Thinkbox\Deadline8\bin\Version 2016-07-04 16:31:37: Network version file: \\ds-storage\DeadlineRepository8\bin\Windows\64bit\Version 2016-07-04 16:31:37: Comparing version files... 2016-07-04 16:31:37: Version files match 2016-07-04 16:31:37: Launching Slave: 2016-07-04 16:31:38: Auto Configuration: Picking configuration based on: dell-c6220-01 / 192.168.1.155 2016-07-04 16:31:38: Auto Configuration: No auto configuration could be detected, using local configuration 2016-07-04 16:31:41: Launcher Thread - Remote Administration is now enabled 2016-07-04 16:31:41: Launcher Thread - Automatic Updates is now enabled 2016-07-04 16:32:22: ::ffff:192.168.1.172 has connected 2016-07-04 16:32:23: Launcher Thread - Received command: SuspendMachine 2016-07-04 16:32:23: Sending command to slave: StopSlave 2016-07-04 16:32:23: Got reply: DELL-C6220-01: Sent "StopSlave" command. Result: "Connection Accepted. 2016-07-04 16:32:23: " 2016-07-04 16:32:26: No Monitor to shutdown 2016-07-04 16:32:26: No Pulse to shutdown 2016-07-04 16:32:26: Launcher Thread - Responded with: Success| 2016-07-04 16:32:31: Launcher Thread - Machine is about to be suspended, shutting down listening port... 2016-07-04 16:32:31: Launcher Thread - OnConnect: Listener Socket has been closed. 2016-07-04 16:34:30: Launcher Thread - Machine is about to be resumed, initializing listening port... 2016-07-04 16:34:30: Launcher Thread - Launcher thread initializing... 2016-07-04 16:44:59: Local version file: C:\Program Files\Thinkbox\Deadline8\bin\Version 2016-07-04 16:44:59: Network version file: \\ds-storage\DeadlineRepository8\bin\Windows\64bit\Version 2016-07-04 16:44:59: Comparing version files... 2016-07-04 16:44:59: Version files match 2016-07-04 16:44:59: Launching Slave:

Slave - (had to be manually started because remote commands failed)

2016-07-04 16:45:00: BEGIN - DELL-C6220-01\render 2016-07-04 16:45:00: Deadline Slave 8.0 [v8.0.4.1 Release (49ce3656c)] 2016-07-04 16:45:04: Auto Configuration: No auto configuration for Repository Path could be detected, using local configuration 2016-07-04 16:45:05: Info Thread - Created. 2016-07-04 16:45:09: Auto Configuration: Picking configuration based on: dell-c6220-01 / 192.168.1.155 2016-07-04 16:45:09: Auto Configuration: No auto configuration could be detected, using local configuration 2016-07-04 16:45:09: Scheduler Thread - Slave initialization complete. 2016-07-04 16:45:09: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-07-04 16:45:10: Scheduler - Job chooser found no jobs. 2016-07-04 16:45:10: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-07-04 16:45:10: Scheduler - Job chooser found no jobs. 2016-07-04 16:45:11: Scheduler Thread - Seconds before next job scan: 6 2016-07-04 16:45:11: Connecting to Slave log: dell-c6220-01 2016-07-04 16:45:12: Listener Thread - fe80::38c8:8bbd:ca27:a683%10 has connected 2016-07-04 16:45:12: Listener Thread - Received message: StreamLog 2016-07-04 16:45:17: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-07-04 16:45:17: Scheduler - Job chooser found no jobs. 2016-07-04 16:45:17: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-07-04 16:45:17: Scheduler - Job chooser found no jobs. 2016-07-04 16:45:18: Scheduler Thread - Seconds before next job scan: 7 2016-07-04 16:45:25: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-07-04 16:45:25: Scheduler - Job chooser found no jobs. 2016-07-04 16:45:25: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-07-04 16:45:25: Scheduler - Job chooser found no jobs. 2016-07-04 16:45:26: Scheduler Thread - Seconds before next job scan: 5 2016-07-04 16:45:31: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-07-04 16:45:31: Scheduler - Job chooser found no jobs. 2016-07-04 16:45:31: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-07-04 16:45:31: Scheduler - Job chooser found no jobs. 2016-07-04 16:45:32: Scheduler Thread - Seconds before next job scan: 6 2016-07-04 16:45:38: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-07-04 16:45:38: Scheduler - Job chooser found no jobs. 2016-07-04 16:45:38: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-07-04 16:45:38: Scheduler - Job chooser found no jobs. 2016-07-04 16:45:39: Scheduler Thread - Seconds before next job scan: 7 2016-07-04 16:45:47: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-07-04 16:45:47: Scheduler - Job chooser found no jobs. 2016-07-04 16:45:47: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-07-04 16:45:47: Scheduler - Job chooser found no jobs. 2016-07-04 16:45:48: Scheduler Thread - Seconds before next job scan: 7 2016-07-04 16:45:55: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-07-04 16:45:55: Scheduler - Job chooser found no jobs. 2016-07-04 16:45:55: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-07-04 16:45:55: Scheduler - Job chooser found no jobs. 2016-07-04 16:45:56: Scheduler Thread - Seconds before next job scan: 6 2016-07-04 16:46:02: Scheduler - Performing Job scan on Primary Pools with scheduling order Pool, Priority, First-in First-out 2016-07-04 16:46:02: Scheduler - Job chooser found no jobs. 2016-07-04 16:46:02: Scheduler - Performing Job scan on Secondary Pools with scheduling order Pool, Priority, First-in First-out 2016-07-04 16:46:02: Scheduler - Job chooser found no jobs. 2016-07-04 16:46:03: Scheduler Thread - Seconds before next job scan: 6

4

Hello Rob,

So I checked into this and this looks like an issue one other customer has seen, and which we have an internal ticket for already. I have added this additional instance to the existing ticket in order to try and speed up a fix.

5

Thanks!

For now I have just left off the power scheduling options so the render machines are always on.

6

Hey folks. Morgan spend some time investigating, and we think we’ve got this solved for the next service pack which should hopefully be out next week (barring any issues).