Hey everyone. This is my first time using deadline. I’m unable to get my first render node to connect to the repository. The render nodes reside in AWS and connect on site with openvpn. I dont have any security groups blocking connections. I am able to ping in both directions, from on site to the aws render node private subnet, and also to the private subnet onsite from the render node.
I’ve installed deadline onsite in a vmware workstation ubuntu 16.04.5 vm.
that vm runs the repository and database, and RCS.
the render node is running centos 7.5. I’ve tried setting up the client to connect with the repository via remote, and also via the file system with an smb share. I will use UBL Licensing
After starting the service, I get this log output.>
[deadlineuser@ip-10-0-1-74 Deadline10]$ cat deadlinelauncher-ip-10-0-1-74-2019-01-25-0003.log 2019-01-25 21:12:25: BEGIN - ip-10-0-1-74.ap-southeast-2.compute.internal\deadlineuser 2019-01-25 21:12:25: Operating System: CentOS Linux release 7.5.1804 (Core) 2019-01-25 21:12:25: CPU Architecture: x86_64 2019-01-25 21:12:25: CPUs: 1 2019-01-25 21:12:25: Video Card: Cirrus Logic GD 5446 2019-01-25 21:12:25: Deadline Launcher 10.0 [v10.0.23.4 Release (e0d42871d)] 2019-01-25 21:12:25: Error encountered when connecting to repository 192.169.0.14:8080;/opt/Thinkbox/certs/Deadline10RemoteClient.pfx: Failed to establish connection to 192.169.0.14:8080 due to a communication error: Could not get response stream (Deadline.Configuration.DeadlineConfigException) 2019-01-25 21:12:25: at c.a (System.String mq, System.Int32 mr, System.Security.Cryptography.X509Certificates.X509Certificate2 ms, System.Security.Cryptography.X509Certificates.X509Certificate2 mt, System.Boolean mu) [0x00224] in <c8f51cc3d060436f9cd772dfd0a72913>:0 2019-01-25 21:12:25: at c..ctor (System.String ml, System.Int32 mm, System.Security.Cryptography.X509Certificates.X509Certificate2 mn, System.Security.Cryptography.X509Certificates.X509Certificate2 mo, System.Boolean mp) [0x001ad] in <c8f51cc3d060436f9cd772dfd0a72913>:0 2019-01-25 21:12:25: at Deadline.StorageDB.RepositoryConnect.RepositoryStorageManager.ConnectToRepository (Deadline.Configuration.RepositoryConnectionSettings connSettings, System.Boolean skipVersionCheck) [0x00069] in <c8f51cc3d060436f9cd772dfd0a72913>:0 2019-01-25 21:12:25: at Deadline.Controllers.DataController.ConnectToRepository (Deadline.Configuration.RepositoryConnectionSettings connectionSettings) [0x00001] in <c8f51cc3d060436f9cd772dfd0a72913>:0 2019-01-25 21:12:25: at Deadline.Controllers.DataController.SetupConnectionSettings (Deadline.Configuration.RepositoryConnectionSettings connSettings) [0x0001e] in <c8f51cc3d060436f9cd772dfd0a72913>:0 2019-01-25 21:12:25: at Deadline.Controllers.DataController..ctor (Deadline.Configuration.RepositoryConnectionSettings connSettings) [0x00037] in <c8f51cc3d060436f9cd772dfd0a72913>:0 2019-01-25 21:12:25: at Deadline.Applications.DeadlineApplicationManager.Connect (Deadline.Configuration.RepositoryConnectionSettings connSettings, System.Boolean updateScriptManager) [0x00042] in <c8f51cc3d060436f9cd772dfd0a72913>:0 2019-01-25 21:12:25: Launcher Thread - Launcher thread initializing... 2019-01-25 21:12:25: creating local listening socket on an available port... 2019-01-25 21:12:25: updating local listening port in launcher file: 43491 2019-01-25 21:12:25: Launcher Thread - Launcher thread listening on port 17000 2019-01-25 21:12:25: Launcher is running as a service or daemon, delaying startup for 60 seconds 2019-01-25 21:12:25: This delay can be adjusted by setting the LauncherServiceStartupDelay setting in the system deadline.ini file 2019-01-25 21:13:25: Launching Slave: 2019-01-25 21:15:46: Launcher Thread - No database connection - cannot update Repository Options 2019-01-25 21:15:46: Launcher Thread - Remote Administration is now disabled since there is no database connection.