AWS Portal license issue

Discussion and Support of Deadline, the Render Management System
LyubomirG
Posts: 14
Joined: Mon Feb 10, 2014 8:14 am
Location: Bulgaria
Contact:

AWS Portal license issue

Postby LyubomirG » Mon Apr 16, 2018 8:38 am

Hello guys,

we are currently exploring the Deadline10 AWS Portal Setup.

After I create infrastructure, I am able to start a Spot fleet. Unfortunately after the slaves spawn they are unable to obtain a deadline license.

error-lic.JPG
error-lic.JPG (12.01 KiB) Viewed 289 times


All I can see in the slave log is this:

slave log.JPG
slave log.JPG (24.15 KiB) Viewed 289 times


We want to use our on premise license server. This is the configuration in the AWS portal settings:

server.JPG
server.JPG (44.89 KiB) Viewed 289 times


Any help is much appreciated!

best,

Lyubo
Lyubomir Grancharov
Operations Manager, Bottleship VFX

eamsler
Posts: 2407
Joined: Thu Dec 16, 2010 1:02 pm
Location: Winnipeg, MB, Canada

Re: AWS Portal license issue

Postby eamsler » Mon Apr 16, 2018 12:30 pm

Actually, I think you may have hit a bug. I'm not sure what causes it yet, but try setting this up in the Automatic Configuration window: (all enabled options here are required)

2018-04-16 12_28_14-Configure Repository Options.png
2018-04-16 12_28_14-Configure Repository Options.png (41.34 KiB) Viewed 284 times


The problem seems to be that the deadline.ini file loses track that it should use the Gateway instance to forward its license traffic. The second option to disable automatic upgrades is just a safeguard. I enabled the license re-write yesterday and it allowed an automatic upgrade to happen, so better be safe than sorry there (takes awhile to pull the upgrade files over the Portal Link.
Edwin Amsler
Head of Support
Thinkbox Software Inc
+1-866-419-0283 ext 804

Winnipeg

eamsler
Posts: 2407
Joined: Thu Dec 16, 2010 1:02 pm
Location: Winnipeg, MB, Canada

Re: AWS Portal license issue

Postby eamsler » Mon Apr 16, 2018 12:50 pm

There is another angle here as well. If using the instances on AWS, there is an option to choose dynamic licensing that you'll need to enable:

2018-04-16 12_49_42-Deadline Monitor  -  C__DeadlineRepository10.png
2018-04-16 12_49_42-Deadline Monitor - C__DeadlineRepository10.png (26.47 KiB) Viewed 283 times


I would only use this after 10.0 SP13 however as there was a socket leak that was corrected recently.
Edwin Amsler
Head of Support
Thinkbox Software Inc
+1-866-419-0283 ext 804

Winnipeg

LyubomirG
Posts: 14
Joined: Mon Feb 10, 2014 8:14 am
Location: Bulgaria
Contact:

Re: AWS Portal license issue

Postby LyubomirG » Tue Apr 17, 2018 7:21 am

Hello Edwin,

thanks for your quick answer! I've tried to implement the solutions you've described but unfortunately no luck yet.

Some screenshots:

log2.JPG
log2.JPG (85.33 KiB) Viewed 259 times


log1.JPG
log1.JPG (109 KiB) Viewed 259 times


Also there is something which might be out of the ordinary. When I start the remote connection server I get the following message which keeps repeating:

Deadline Remote Connection Server 10.0 [v10.0.13.6 Release (60bd5de8a)]
Connected to "\\cache\Deadline10RepoTest"
Listening for TLS connections on 0.0.0.0:4433...
Legacy bypass backend started. Listening on port 51685.
Listening for HTTP requests on port 8080...
[10.1.10.10] GET http://10.1.10.10:8080 [Forbidden]
[10.1.10.10] GET http://10.1.10.10:8080 [Forbidden]
[10.1.10.10] GET http://10.1.10.10:8080 [Forbidden]
[10.1.10.10] GET http://10.1.10.10:8080 [Forbidden]
[10.1.10.10] GET http://10.1.10.10:8080 [Forbidden]
[10.1.10.10] GET http://10.1.10.10:8080 [Forbidden]
[10.1.10.10] GET http://10.1.10.10:8080 [Forbidden]
[10.1.10.10] GET http://10.1.10.10:8080 [Forbidden]
[10.1.10.10] GET http://10.1.10.10:8080 [Forbidden]

best regards,
Lyubomir Grancharov
Operations Manager, Bottleship VFX

eamsler
Posts: 2407
Joined: Thu Dec 16, 2010 1:02 pm
Location: Winnipeg, MB, Canada

Re: AWS Portal license issue

Postby eamsler » Tue Apr 17, 2018 10:04 am

Ah, okay. The problem might be here that you're using dynamic licensing without dynamic licenses. Turn off all of that and the Slaves should try and use the licenses that are being forwarded through Portal Link.

Also, change your "license server" to be 10.128.2.4 as that's the private IP of the Gateway machine that'll forward your requests over Portal Link.

The forbidden messages are actually normal, and I've opened an issue here to see if we can silence it.


Something to be mindful of here that can catch people off guard (and is unrelated to what we're working on here) is that the infrastructure costs money to have running. If you're not already, I would stop the infrastructure between tests. The settings we're applying here will persist across infrastructures. This page on the AWS side is great for seeing where the dollars and cents are going:
https://console.aws.amazon.com/billing/home
Edwin Amsler
Head of Support
Thinkbox Software Inc
+1-866-419-0283 ext 804

Winnipeg

cmoore
Posts: 82
Joined: Tue Feb 03, 2015 10:50 am

Re: AWS Portal license issue

Postby cmoore » Mon Apr 23, 2018 12:11 pm

I suspect the issue here is that in the auto configuration you are setting 10.128.2.4. The syntax needs to be 27008@10.128.2.4. 27008 is the default port of the license server, if you manually specified otherwise you would need to change that value to what you set.

LyubomirG
Posts: 14
Joined: Mon Feb 10, 2014 8:14 am
Location: Bulgaria
Contact:

Re: AWS Portal license issue

Postby LyubomirG » Tue Apr 24, 2018 2:06 am

Hello,

the problem is that when I use 27008@10.128.2.4 instead of just 10.128.2.4 the slaves won't appear on the deadline monitor anymore.

best,

Lyubo
Lyubomir Grancharov
Operations Manager, Bottleship VFX

LyubomirG
Posts: 14
Joined: Mon Feb 10, 2014 8:14 am
Location: Bulgaria
Contact:

Re: AWS Portal license issue

Postby LyubomirG » Tue Apr 24, 2018 7:26 am

Hi guys,

today I did a fresh installation of the remote server and the AWSPortalLink. I've used the 27008@10.128.2.4 as a license gateway and it seems to be working this time! The license server indicates that the slaves are obtaining licenses. However, when I spawn two slaves with the premade 3ds Max + V-ray image provided by Deadline I m unable to render.

Going to attach a slave log file for you to review.

Thanks a lot for your assistance!

best,

Lyubo
Attachments
slave.txt
(13.87 KiB) Downloaded 14 times
Lyubomir Grancharov
Operations Manager, Bottleship VFX

LyubomirG
Posts: 14
Joined: Mon Feb 10, 2014 8:14 am
Location: Bulgaria
Contact:

Re: AWS Portal license issue

Postby LyubomirG » Thu Apr 26, 2018 3:25 am

Hello guys,

this issue was resolved. Apparently 3ds Max needed Usage Based Licensing in order to rend.

Thanks a lot for your help!

best,

Lyubo
Lyubomir Grancharov
Operations Manager, Bottleship VFX

eamsler
Posts: 2407
Joined: Thu Dec 16, 2010 1:02 pm
Location: Winnipeg, MB, Canada

Re: AWS Portal license issue

Postby eamsler » Mon Apr 30, 2018 10:04 am

Ah! Yes, that'll do it. I'm somewhat surprised that the Slaves went into license-free mode though...

Is there something we can do to make that error more obvious in the future?
Edwin Amsler
Head of Support
Thinkbox Software Inc
+1-866-419-0283 ext 804

Winnipeg


Return to “Thinkbox Software - Deadline”

Who is online

Users browsing this forum: No registered users and 4 guests