Hi,
I’ve updated out deadline install from 10.0 to 10.1 today and it is working for all machines but one. We’re on a mixed windows osx environment for the workers and with the repository and remote connection server on windows.
For some reason I can’t get this one worker (Mac) to connect to the repository through RC. Other mac’s do work. I’ve first updated the repository and rcs and then relied on the automatic updater to update the clients. This didn’t work on all machines but it did one the one giving me trouble now. It was working, automatically downloaded and installed the update and then it was no longer able to connect.
Anyone have as a clue to what might be causing this?
I wouldn’t focus to much on this error if that is the ip address of the machine running AWS Portal Link:
[tls_conn#1] Connection accepted from 10.30.1.52:49443; starting TLS negotiation. (1 total connections)
[tls_conn#1] Error: Authentication failed because the remote party has closed the transport stream. (IOException)
[tls_conn#1] Connection closed. (0 total connections)
When AWS Portal Link tests the connection to the TLS, it poorly validates and creates this error. You will notice every time this line is printed in “AWSPortalLink\AWSPortalLink-hostname-2019-10-23-0000.GetTunnelParams.log”
1571863758.821000 2019-10-23 15:49:18,821 [C:\Program Files (x86)\Thinkbox\AWSPortalLink\GetTunnelParams.py:_get_rcs_info:188] [root] [18492] [MainThread] [INFO] Successfully connected to Connection Server at u’10.127.245.19’:4433
That that TLS error will be generated in the RCS.
These errors you are reporting look like they are coming from the Deadline Monitor log (Not the Worker), can you please confirm?
2019-10-18 09:27:05: Error when attempting to communicate with the CentralServer on your Infrastructure: Status(StatusCode=DeadlineExceeded, Detail=“Deadline Exceeded”)
2019-10-18 09:27:10: The specified log group already exists
What I would specifically focus on here is the Asset Server Controller log for access errors and the AWS Portal Link log ssh tunnel errors:
“C:\ProgramData\Thinkbox\AWSPortalLink\AWSPortalLink-hostname-2019-10-23-0000.log”
“C:\ProgramData\Thinkbox\AWSPortalAssetServer\logs\awsportalassetserver_controller.log”
Hope that helps.
I’m not using AWS portal. all workers are on our LAN. But as I’ve also opened a support ticket let’s keep communication in one place and continue there.