AWS Thinkbox Discussion Forums

Monitor won't start (Linux)

Hi!
I have the following setup: Deadline 10.1.18.4 on Centos 7, launcher running as a daemon.
My problem is that the icon to open the monitor doesn’t work. This is what happens when I execute the command from the .desktop file in a terminal:

$ /opt/Thinkbox/Deadline10/bin/deadlinelauncher -monitor
daemon was not added to the CommandLineParser.
daemon was not added to the CommandLineParser.
Port 17000 is already in use
Another Launcher is already running
Shutting down

When I open the monitor directly (deadlinemonitor) the application window shows up.

We have been using Deadline 9 until now where the monitor can easily be opened using the desktop icon as well as using a command similar to the one above in a terminal window:

$ /opt/Thinkbox/Deadline9/bin/deadlinelauncher -monitor
Port 17090 is already in use
Another Launcher is already running
Launching Monitor directly because the existing Launcher is running as a daemon
Shutting down

(the monitor then continues to start and print some more stuff, but the main difference is that with Deadline 10 there’s no “launching monitor directly…” anymore and the monitor doesn’t show up)

In Deadline 9, the launcher log shows this when I try to open the monitor:

2021-09-29 14:55:49:  ::1 has connected
2021-09-29 14:55:49:  Launcher Thread - Received command: GetRunningAsDaemon
2021-09-29 14:55:49:  Launcher Thread - Responded with: Success: True

However, in Deadline 10, this show up instead:

2021-09-29 15:07:52:  Launcher Thread - ::1 has connected
2021-09-29 15:07:52:  Launcher Thread - Received command: GetRunningAsDaemon
2021-09-29 15:07:52:  Launcher Thread - Responded with: Success: False
2021-09-29 15:07:52:  Launcher Thread - ::1 has connected
2021-09-29 15:07:52:  Launcher Thread - Received command: LaunchMonitorPromptForUpgrade
[some lines about auto update removed]
2021-09-29 15:07:52:  Launching Monitor
2021-09-29 15:07:52:  Launcher Thread - Responded with: Success

The question is: why is the launcher claiming it’s not running as a daemon, when it actually is? It is running as its own user (not root and not the one I’m logged in as). But this has worked perfectly fine with Deadline 9.

Kind regards
Stefan

1 Like
Privacy | Site terms | Cookie preferences