Machine Name Command Time Stamp Status Results
Render-i7-06 ShutdownMachine 2/20 14:55 Failed No connection could be made because the target machine actively refused it 192.168.94.31:5042
[code]ping 192.168.94.31
Pinging 192.168.94.31 with 32 bytes of data:
Reply from 192.168.94.31: bytes=32 time<1ms TTL=128
Reply from 192.168.94.31: bytes=32 time<1ms TTL=128
Reply from 192.168.94.31: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.94.31:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
[/code]
This is the error I get now when I try to shut down machines manually from either of our pulse-ready machines. My desktop will however shut them down. No idea why it stopped working.
If it works from one machine, and not another, I would guess it’s some sort of network issue. However, since you can ping it, that leaves me scratching my head. Does it work if you ping it by host name?
We didn’t change anything in the remote control commands since beta 11, so I’m not sure why this would all of a sudden stop working…
Just thought of something. Have you performed these steps on your Pulse machines since you had beta 6 or earlier on them?
I noticed the port it’s trying to use is 5042. That’s the old default port before we made the changes to allow concurrent major Deadline versions to run on the same machine. For Deadline 6, the default port is actually 17060. If that machine is sending a command to a different port than the launcher is listening on, that would explain the error. It’s likely your desktop has the new port, and that’s why it works.
Oh I uninstalled and re-installed during the upgrade but I used our old INI since it had the pulse auto-start INI settings. Let me flush the port values which came along with those old settings.