AWS Thinkbox Discussion Forums

AWS - General Queries

Hi,

I seem to have most things working on AWS with Deadline10 now, just a few issues if anyone has any info?

Corona licensing on the render instances? - Is it possible to get the AWS instances to talk to the Corona license server? I have Vray setup and that works fine (I can see the instances grab a license from the server in the office), but nothing for Corona.

I specified the ports in the Infrastructure tab, and the instances are pointing to the license server, but the job just fails as it can’t get a license.

Remote connections to the AWS instances? - Is it possible to connect to these instances via rdp? They don’t have a public ip address.
I can send remote and deadline commands but can’t get on them to have a look what they are up to.

Thanks for any pointers on these.

When forwarding ports, you’ll have to point apps to the Gateway instance at IP 10.128.2.4 and that should get you there.

For forwarding RDP, I haven’t played with this yet. I don’t believe we have the right networking set up that you can just attach a public IP to the instance, but we do have these docs:
docs.thinkboxsoftware.com/produ … laves.html

Hi Edwin,

It looks like I had to point Corona to the Gateway instance, and then setup some port forwards in the Infrastructure dialog:

[attachment=0]capture.jpg[/attachment]

Also, I’ve noticed the slaves will hang about for a few minutes once the 3dsmax port forwarder kicks in, is this normal? It’s 4 minutes of just waiting.

Relevant bit of log file starred:

2018-08-17 16:22:13: 0: INFO: Starting monitored managed process 3dsmaxProcess 2018-08-17 16:22:13: 0: INFO: Stdout Redirection Enabled: True 2018-08-17 16:22:13: 0: INFO: Stdout Handling Enabled: True 2018-08-17 16:22:13: 0: INFO: Popup Handling Enabled: True 2018-08-17 16:22:13: 0: INFO: QT Popup Handling Enabled: True 2018-08-17 16:22:13: 0: INFO: WindowsForms10.Window.8.app.* Popup Handling Enabled: True 2018-08-17 16:22:13: 0: INFO: Using Process Tree: True 2018-08-17 16:22:13: 0: INFO: Hiding DOS Window: True 2018-08-17 16:22:13: 0: INFO: Creating New Console: False 2018-08-17 16:22:13: 0: INFO: Running as user: IP-0A803D60$ 2018-08-17 16:22:13: 0: INFO: Executable: "C:\Program Files\Autodesk\3ds Max 2018\3dsmaxio.exe" 2018-08-17 16:22:13: 0: INFO: Argument: -p "C:\Windows\SERVIC~2\NETWOR~1\AppData\Local\Temp\dl_589334427496.ini" -q -s -secure off "C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Thinkbox\Deadline10\cache\AboLy9iNSNbvdsCWV7J4G0fx0\maxStartup\2018\deadlineStartupMax2018.max" 2018-08-17 16:22:13: 0: INFO: Full Command: "C:\Program Files\Autodesk\3ds Max 2018\3dsmaxio.exe" -p "C:\Windows\SERVIC~2\NETWOR~1\AppData\Local\Temp\dl_589334427496.ini" -q -s -secure off "C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Thinkbox\Deadline10\cache\AboLy9iNSNbvdsCWV7J4G0fx0\maxStartup\2018\deadlineStartupMax2018.max" 2018-08-17 16:22:13: 0: INFO: Startup Directory: "C:\Program Files\Autodesk\3ds Max 2018" 2018-08-17 16:22:13: 0: INFO: Process Priority: BelowNormal 2018-08-17 16:22:13: 0: INFO: Process Affinity: default 2018-08-17 16:22:13: 0: INFO: Process is now running 2018-08-17 16:22:13: 0: INFO: Waiting for connection from 3dsmax ***2018-08-17 16:22:31: Port Forwarder (max:27002): Client connected to port forwarder. ***2018-08-17 16:22:31: Slave - Confirmed Credit Usage for "max". ***2018-08-17 16:22:42: Port Forwarder (max:2702): Client connected to port forwarder. ***2018-08-17 16:26:26: 0: STDOUT: - 16:26:26.000 INFO: Begin setting up global configuration 2018-08-17 16:26:26: 0: STDOUT: - 16:26:26.015 INFO: End setting up global configuration 2018-08-17 16:26:26: 0: STDOUT: - 16:26:26.015 INFO: Begin initialize system watcher to detect file changes 2018-08-17 16:26:26: 0: STDOUT: - 16:26:26.015 INFO: End initialize system watcher to detect file changes 2018-08-17 16:26:26: 0: STDOUT: - 16:26:26.015 INFO: Begin loading assemblies

Thanks again.

That four minutes is Max “getting ready” as far as I know. I have the same issue when I launch the UI after a fresh reboot. Or, that’s been my assumption. Just to challenge that, do you see it when the cloud render node picks up its second job?

It looks like it just ploughs on with the job after that initial task is complete, so nothing to worry about in the long run.

Are we able to get logs on what is happening with the slave instances before they start a job? I know they all wait for the files to get uploaded, but can we see that logged somewhere.

Thanks.

As of today, the “connect to Slave log” from the machine running AWS Portal Link is the best way. It’ll give you a live few into what the Slave itself is doing, but not into the transfer queue.

For the queue of files being transferred, you can check the AWS Portal Asset Server logs for that one.

Thanks Edwin, thought it might be hiding somewhere.

Few last bits if you don’t mind :slight_smile:

Are there any options to specify the render limits in SMTDSettings so I can add specific limits to our cloud jobs?

I thought it might be:

SMTDSettings.LimitGroups = “maxcloud, deadline”

but that didn’t pick any up.

Also, where do I specify auxiliary files to upload with the job? I got an error message saying Xrefs needed adding to the job. At the moment I’m just merging everything, but if I want to get it farm friendly, I would prefer everything to be kept separate.

Thanks again!

I’m moving that over here

Privacy | Site terms | Cookie preferences