Feature Request: Launch the "Launcher" from the monitor

Deadline
1

I was rolling out a new version of Nuke to our farm via the “Remote Control” and then “Execute Command.” I have a .bat file that silently installs Nuke. I noticed that a few machines got errors saying the connection had been actively refused. After browsing these forums, I found out that this error was caused because the Deadline Launcher was not running on those machines. To be clear, these machines had the “Slave” running, but not the “Launcher.”

So… I was wondering if it would be possible to launch the “Launcher” from the Deadline Monitor via “Remote Control” or something similar. That would alleviate having to script this feature, or to remote in to hundreds of machines whenever a new version of something needs to be rolled out.

Thanks!

2

The launcher actually facilitates the remote control (ie: when you send a remote command to a machine to run a batch file or launch the slave, you’re talking to the launcher on the other end). So if the launcher isn’t running, who do you talk to to start the launcher? :slight_smile:

The launcher should be set to start at login, so that helps to ensure it’s always running. Any idea why the launcher wasn’t running on some of your machines? I’m wondering if maybe it crashed, in which case we should look at the logs to figure out what happened.

Cheers,

  • Ryan