I have been trying to setup AWS Portal over the last few days and I’ve made some progress but have hit up against a problem I can’t seem to fix.
Both the AWS Portal Link and AWS Asset Server are showing as Online & green, however once I create an Infrastructure the AWS Asset Server goes offline. I assumed that this was a firewall/anti-virus issue at first, however disabling them doesn’t make any difference. I then assumed that there was a communication (or permission) error between the Asset Server and the S3 bucket, however if I manually upload files/folder to the S3 bucket through the console & stop the Infrastructure, selecting ‘empty the bucket’ does delete those files.
I can upload some of the log files but to be honest, I’m not sure which ones would be most useful to troubleshoot this!
Any help or advice on what to look into next would be greatly appreciated.
i’ve got this to work before and we’ve successfully rendered with aws portal and aws slaves, but recently the asset server start to fail to transfer assets to the ec2 platform, and now after upgrading deadline to 10.1.5.1, i’m getting the same exact error.
AWS Portal Link and AWS Asset Server both reporting online before creating an infrastructure.
ADter an infrastructure is created, AWS Portal Link is Online, but AWS Asset Server reports “Not Connected”
This is the repeated log from the console: Error when attempting to communicate with the CentralServer on your Infrastructure: Status(StatusCode=DeadlineExceeded, Detail="Deadline Exceeded")
If you’re on 10.1.5.1. try replacing "C:\Program Files (x86)\Thinkbox\AWSPortalLink\sshlib\command_factory.py" with command_factory.py (12.6 KB). that should resolve the issue with the Asset Server and Portal link not showing connected.
Be sure to stop the services before you make the swap, and start them back up again. Then try firing up another infrastructure. If that doesn’t work, please reach out to us by one of the options on the support page. We’d love to be quick and active in the forums, we’re just not there yet.
Actually a member of your support team sent me the very same file and it has fixed the issue!
I have now been able to successfully submit and render on a Spot Fleet, so I’m very happy.
@Masonry_Studios - I would suggest following Justin’s advice on the command_factory.py file. Although I also had another issue where the DashKey on my local machine wasn’t permitting ssh connections so I had to manually delete and reinstall.
@AJ_Jefferies Hey! It worked! Omg what a fix this was. Thank you so much for letting me jump in on this thread. I’m happy to hear that you managed to get yours up and running too!
Now i’m off to trying and figure out how to create my own AMI. Cause the plugins on the default deadline AMIs are older than the ones we use.
I’ve been having this same problem, yet replacing the file didn’t work for me. I keep getting both the AWS Portal Link and AWS Asset Server offline when creating an infrastructure. Its the first time I try to run one.
Is there anything else I can try?
I would really appretiate your help. I have several days trying to set it up to run my operations on AWS.
I’m also experiencing this issue with version 10.1.92. I have tried replacing the command_factory.py file and while that did get the AWSPortalLink installer to successfully create the DashKey and Dashkey.pub files, the same error: Error when attempting to communicate with the CentralServer on your Infrastructure: Status(StatusCode=DeadlineExceeded, Detail="Deadline Exceeded")
Could you share the whole log you’re seeing those errors in? I haven’t seen that out of 10.1.9.2 AWSPortal, so it’s possible there’s something else going on.
Hi Justine,
I have the same problem that the asset server went offline after setup infrastructure. I’m using Deadline Version (ex: 10.0.3.2): Deadline -10.1.10.6. I have logged the case with AWS but no response so far. It has been 2 days.
I’m not sure what’s gone wrong on the Premium Support side of things but let us worry about that.
Looking at the screenshots the issue looks like you don’t have an S3 bucket (there should be info in the “Asset Server S3 Bucket” field).
Stop your infrastructure and go to Tools->Configure Asset Server and hit ‘Create New Bucket’. Then remove the existing root directory entry and hit ok. Then go back into Configure Asset Server and add it again, this will run an end-to-end test of the root directory added. If it fails, go to %PROGRAMDATA%\Thinkbox\AWSPortalAssetServer\logs\ and check that log for errors.
If it does fail, my first guess would be that the D: drive is a network drive and needs to be added under Tools->Configure Repository Options->Mapped Drives.
I’m going to be on vacation for the rest of the week so I won’t be keeping an eye on the forums. So maybe send your logs and findings into a ticket at https://awsthinkbox.zendesk.com/hc/en-us. Or call us at 1-866-419-0283 between 9-5CST.
Hi, I am having the same problems, I have started to install and configure the asset server, in the image I have put the ip of the server that hosts deadline and asset server and portal, we are using Deadline 10.2.0.10
-From asset server we are using a route by smb hosted on a Nas system.
-I don’t know if there is an extra port to open or if something is blocking.
Wed Feb 15 13:23:03 UTC 2023 -- Gateway configured to connect to RCS via HTTPS with SSL verification disabled.
Wed Feb 15 13:21:02 UTC 2023 -- Could not connect to the RCS. Connection response: '<html><head><title>502 Bad Gateway</title></head><body bgcolor="white"><center><h1>502 Bad Gateway</h1></center><hr><center>nginx/1.12.2</center></body></html>'
