We just recently upgraded Deadline and it appears that Pulse has not been installed.
Is this an optional install now?
If so, where can I find the installer?
I noticed that it is present in: DeadlineRepository10/bin/Windows/64bit/bin.zip
But it doesn’t look as straight forward as copying it from that location as there are missing python libraries that I would also have to merge in.
Hello,
I Have same problem
But I copy 3 files from “DeadlineRepository10\bin\Windows\64bit\bin” → “C:\Program Files\Thinkbox\Deadline10\bin” :
deadlinepulse.deps.json
deadlinepulse.dll
deadlinepulse
and copy folder “DeadlineRepository10\bin\Windows\64bit\bin\python3_new\UI\DeadlinePulse” → “C:\Program Files\Thinkbox\Deadline10\bin\python3\UI”
Now you can execute C:\Program Files\Thinkbox\Deadline10\bin\deadlinepulse.exe
This fixed my pulse not updating from 10.1.23.6 to 10.4.0.10, so thank you very much.
Thank you very much, but the operation of using Pulse to shut down the computer after rendering is completed has not taken effect. Although Pulse prompts that a shutdown is to be performed, it does not work and only serves as a reminder.
I used this and, sure, Pulse does run – but it does not actually function as required (and as we have been relying on it for years). I have Remote Administration checked with Redirect Remote Command through Pulse, and no Global Remote Command Port overrides set anywhere. Pulse (and Monitor redirected through Pulse) attempts the command and times out, and the logs seem to suggest that the wrong port is being addressed.
My guess (I have not yet chased this rabbit to ground) is that somewhere an .ini file is not being written or read, so that either Pulse itself or the Monitor/Worker is failing to discover, address, or listen on what should be an agreed-upon port.
Additionally, though possibly separately, after I implemented this solution my Deadline installs that ran Pulse began having Launcher/Worker failures after restart due to inability to read .ini files in the ApplicationData.…\ store. This problem did not occur before 10.4 update (I’m at 10.4.1.8), and I do not think it occurs except where I have attempted this Pulse fix.
Long story short, this fix (while a helpful suggestion!!!) does not seem to actually solve the problem AND it seems that an essential part of our implementation of Deadline has been broken at 10.4 without adequate documentation, workarounds, or alternatives.
Somebody please advise!
[example log entry below, ‘nnn’ replacing local subnet IP address, which is correct]
could not connect to machine at nnn.nnn.nnn.nnn:17000 because: No connection could be made because the target machine actively refused it.. Machine may be turned off, Launcher may not be running, or RemoteControl may be set to Blocked on the machine. If you've checked all of those, please try to override the IP address of the Worker machine.You can right click the Worker and select "Modify Worker Properties..." and enter the proper IP address in the "Host Name/IP Address Override" textbox.
Another piece of the solution may be (for those of us running silent installs) to add an explicit unblocking option to the installer command line–ref. DeadlineLauncher Remote Command Not Work - #5 by gdtech
I’m happy to report that this problem seems to have been an artefact of my experimenting on those machines; clean reinstalls with the fixes mentioned above ( copies as per @MoPA and adding the --remotecontrol UnBlock to the silent install command line) seem to have done the job.
(PSA – for some reason “UnBlock” is case-sensitive and will cause a silent install to hang with a GUI error message!!!)