Deadline Worker not connecting to Remote Connection Server/Repo

Hi,

I am trying to create a render farm in AWS using Deadline and I am having issues getting the workers to connect successfully to the Main Server (with Deadline Client, Repo, MongDB and RCS installed).

I configure the worker with these commands:

# Setup Deadline
source "/etc/profile.d/deadlineclient.sh"
DEADLINE_COMMAND="$DEADLINE_PATH/deadlinecommand"
"$DEADLINE_COMMAND" -SetIniFileSetting KeepWorkerRunning True
"$DEADLINE_COMMAND" -SetIniFileSetting LaunchSlaveAtStartup True
"$DEADLINE_COMMAND" -SetIniFileSetting ProxySSLCertificate /var/lib/Thinkbox/Deadline10/Deadline10RemoteClient.pfx
"$DEADLINE_COMMAND" -SetIniFileSetting ProxyRoot myserver.atmydomain.biz:4433
"$DEADLINE_COMMAND" -SetIniFileSetting ProxySSLCA
"$DEADLINE_COMMAND" -SetIniFileSetting ClientSSLAuthentication Required
"$DEADLINE_COMMAND" ChangeRepository Proxy myserver.atmydomain.biz:4433 /var/lib/Thinkbox/Deadline10/Deadline10RemoteClient.pfx render
service deadline10launcher restart

The ChangeRepository command completes successfully but when the service restarts I can see the following error in the logs.

2022-01-28 13:01:40:  Operating System: Linux
2022-01-28 13:01:40:  CPU Architecture: x86_64
2022-01-28 13:01:40:  CPUs: 2
2022-01-28 13:01:40:  Video Card: Cirrus Logic GD 5446
2022-01-28 13:01:40:  Deadline Launcher 10.1 [v10.1.20.3 Release (1a0d97d0f)]
2022-01-28 13:01:40:  WARNING: Failed to retrieve binary Machine configuration. Deadline may be improperly configured, and might fail to connect.
2022-01-28 13:01:40:  Full error message: Permission denied
2022-01-28 13:01:40:  Error encountered when connecting to repository myserver.atmydomain.biz:4433;/var/lib/Thinkbox/Deadline10/cert/Deadline10RemoteClient.pfx: Object reference not set to an instance of an object. (System.NullReferenceException)
2022-01-28 13:01:40:     at Deadline.Launcher.Launcher.ChangeRepository(RepositoryConnectionSettings updatedSettings)
2022-01-28 13:01:40:     at Deadline.Launcher.Launcher.CheckForConnectionUpdate(Boolean verbose)
2022-01-28 13:01:40:  WARNING: PythonSync (Python 3) upgrade failed with the following error:
2022-01-28 13:01:40:  Object reference not set to an instance of an object.
2022-01-28 13:01:40:  WARNING: PythonSync (Python 2) upgrade failed with the following error:
2022-01-28 13:01:40:  Object reference not set to an instance of an object.
2022-01-28 13:01:40:  Launcher Thread - Launcher thread initializing...
2022-01-28 13:01:40:  Launcher Thread - opening remote TCP listening port 17000
2022-01-28 13:01:40:  Launcher Thread - creating local listening TCP socket on an available port...
2022-01-28 13:01:40:  Launcher Thread - local TCP port bound to: [::1]:36319
2022-01-28 13:01:40:  Launcher Thread -  updating local listening port in launcher file: 36319
2022-01-28 13:01:40:  Launcher Thread - Launcher thread listening on port 17000
2022-01-28 13:01:40:  Launching Worker:
2022-01-28 13:01:41:  WARNING: Failed to retrieve binary Machine configuration. Deadline may be improperly configured, and might fail to connect.
2022-01-28 13:01:41:  Full error message: Permission denied
2022-01-28 13:01:41:  Launcher Thread - No database connection - cannot update Repository Options
2022-01-28 13:01:41:  Launcher Thread - Remote Administration is now disabled since there is no database connection.

Can you give any direction on what is wrong? or what I can change to get the worker to communicate?

Thanks again,

If I’m reading this right, the client isn’t able to read the machine level dconf file due to a lack of permissions. It’ll be in /var/lib/Thinkbox/Deadline10/, check the permissions on it there.

If that doesn’t solve it, could you create a ticket at awsthinkbox.zendesk.com? We’ve got better mechanisms to follow up in the ticket system over the forums at the moment.

Hi, I’m getting the same thing with a fresh deadline10.2.1.1 from a renderfarm machine and a network share deadline client install. Works fine from a user workstation. Any Idea?