We using the 10.4.1.8 version Deadline for our farms,Now I find the remote command not running ,then find the deadline launcher listenning port ,The linstenning port 17000, by IPv6 ,not IPv4,And then I check the old version of deadline 10.2.1.1,on the 10.2.1.1 node ,the deadlinelauncher is listenning by IPv6 and IPv4 ,So what happend of the 10.4.1.8 version ?
Edit the deadline.ini in the “C:\ProgramData\Thinkbox\Deadline10” path,
Remote command enabled set RemoteControl=NotBlocked.
Remote command disabled set RemoteControl=Blocked
Updating to 10.4.1.8, I’m having the same issue but I have an error log mentioning:
An unexpected error occurred while Restart Remote Worker(s):
Specified argument was out of the range of valid values. (Parameter ‘port’) (System.ArgumentOutOfRangeException)
I also noticed the new RemoteControl=NotBlocked parameter in the deadline.ini file, but it doesnt seem to solve the issue
Wait, so rather than the multiple settings in the Repository Options under Monitor, we’re going to manually edit .ini files per client with a clumsy on/off?
That cannot be the answer. (even if it is–it’s insane!)
Unfortunately, it’s the closest thing to documentation I can find, so far, for this breaking change.
OK, grinding away at it again some more…
I think for those of us who have scripted silent installs (and therefore never actually see the GUI install wizard) this is more opaque than it is for others, because the change was not well documented (and “added a setting that silently overrides the settings but did not update the settings themselves or report that as the cause in the logs” is just not the sort of thing it would occur to me to do!).
Looks like adding another option to the explicit option set at install is the way to go, here.
--remotecontrol <remotecontrol>: Remote Control is a Deadline feature that allows remote users to administer a machine that is running the Launcher. This includes running arbitrary commands. We recommend that you block this feature on workstations, servers, and other machines that are not dedicated render nodes. Default: Blocked. Allowed: Blocked NotBlocked.
That probably doesn’t solve everything–like Pulse not actually being installed???–but it should correct this. Will test and update if any problems.
This appears to have solved the problem for me.
(PSA – for some reason “UnBlock” is case-sensitive and will cause a silent install to hang with a GUI error message!!!)
It’s weird that setting the .ini file with the same setting doesn’t fix the issue but from the installer it does…
I’ll test the setting from the installer rather than editing the .ini file…
Nah it’s still not working for us.
Forcing --remotecontrol NotBlocked during installation or setting it directly from deadline.ini doesn’t make any difference.
We are still getting the same error Logs:
An unexpected error occurred while Restart Remote Worker(s):
Specified argument was out of the range of valid values. (Parameter ‘port’) (System.ArgumentOutOfRangeException)
at System.Net.IPEndPoint…ctor(IPAddress address, Int32 port)
at Deadline.RemoteCommands.RemoteCommand.c(String azm, Int32 azn, Boolean azo)
at Deadline.RemoteCommands.RemoteCommand…ctor(DataController azg, String azh, String azi, RemoteCommandTimeout azj, Int32 azk)
at Deadline.RemoteCommands.RemoteCommand.SendLocalCommand(Int32 port, String commandText, RemoteCommandTimeout timeout)
at Deadline.Launcher.LauncherUtils.SendLauncherCommandsToSelf(RemoteCommandTarget target, DataController dataController, String commandText, Boolean checkIfUpgradeNecessary, RemoteCommandTimeout timeout, Boolean waitForReply, MessageCollection& responses, ExceptionCollection& exceptions, RemoteCommand[ ]& sentCommands)
at Deadline.Launcher.LauncherUtils.SendSlaveLauncherCommands(DataController dataController, SlaveInfoSettings[ ] slaveInfoSettings, RemoteCommandType command, String argument, Boolean appendConfigName, RemoteCommandTimeout timeout, Boolean waitForReply, MessageCollection& responses, ExceptionCollection& exceptions, RemoteCommand[ ]& sentCommands, Boolean checkForSelf)
at Deadline.Monitor.WorkItems.RemoteCommandWI.SendSlaveLauncherCommand(SlaveInfoSettings[ ] infoSettings, Boolean appendConfig)
at Deadline.Monitor.WorkItems.RemoteRestartSlaveWI.InternalDoWork()
at Deadline.Monitor.MonitorWorkItem.DoWork()
We updated our Production to 10.4.1.10 and it seems like RemoteControl is working fine for us…
I really don’t understand why our Lab setup isn’t working with RemoteControl… At least it’s working in production for us