Remote commands are failing pretty often from “timed out while waiting”. Did the timeout duration get reduced?
Also is there a way to execute it as administrator?
Nope, all these commands still have a 40 second timeout, and that hasn’t changed for a long time.
The commands are always executed as the user that the Launcher is running as, so the Launcher would have to be running as admin to get the commands to run as admin.
Cheers,
- Ryan
Gavin,
Have you looked at the new maintenance job type to execute any code? The remote commands are handy to a point, but I wouldn’t depend on them for software deployment/code execution. Too many platform/silly Windows specific potentials gotchas. You could wrap any code as an executable with domain admin or whatever rights and yet run the exe from a maintenance plugin which itself is executed by the locally running slave, which may be another user.
I was planning to but couldn’t find how to submit one.
I’m getting this error in like 1-2 seconds. Bug?
Can you post the timeout error message? Maybe the DNS resolution is timing out quickly. Deadline’s timeout only kicks in after a connection has been established, and it’s waiting for a response from the remote machine.
Machine Name Command Time Stamp Status Results
Render-i7-01 Execute "C:\Windows" 2013/10/03 11:40:19 Failed error occurred while reading reply: timed out while waiting for data (FranticX.Net.SimpleSocketTimeoutException)
Thanks! That’s definitely coming from Deadline, and I was able to track down the problem.
This will be fixed in beta 7.
Cheers,
- Ryan