Author Topic: License bug using DL/EC2  (Read 4714 times)

2016-11-22, 16:12:21

JCdeBlok

  • Active Users
  • **
  • Posts: 85
  • Jonathan de Blok
    • View Profile
Im in the middle of Deadlining my EC2 farm and I'm having some issues with Corona's lic:


This is from the slave log, complaning it's can find a lic on the lic server:

2016-11-22 15:03:17 [BEGIN] initializing license for application 3dsmax. Our request key is: [xxx]
2016-11-22 15:03:17 Reading an activation file located at C:\Users\[user]\AppData\Local\CoronaRenderer\CoronaActivation.txt. It contains: LS:10.0.0.100.
2016-11-22 15:03:17 Trying to connect to licensing server at 10.0.0.100.
2016-11-22 15:04:17 Licensing server did not respond in 60 seconds, aborting.
2016-11-22 15:04:17 Current license is:
                        No active license found.
                        Error: Hardware configuration changed. Please reactivate.
2016-11-22 15:04:17 [END] Activation process done.



But on the the lic server side:

2016-11-22 15:03:18   Got request key [xxx] for application 3dsmax from IP-A0068
2016-11-22 15:03:19   Replying with '[xxxx]' to IP-A0068
2016-11-22 15:03:19   Host IP-A0068 successfully accepted the license.


(I've removed the the keys and hashes and replaced them with [xxx])


And ofcoase Corona isn't going to do any rendering and throws an exepection to deadline:

RenderPluginException -- Error: RenderTask: Unexpected exception (Failed to open the max renderer.


Any clues? All firewalls are down.

2016-11-23, 11:33:47
Reply #1

JCdeBlok

  • Active Users
  • **
  • Posts: 85
  • Jonathan de Blok
    • View Profile
Fixed it! Not sure how, some AWS networking voodoo.. but for future ref: make sure all instances are using the same VPC security group and all have 'source/dest check' enabled.



2016-11-23, 13:01:07
Reply #2

JCdeBlok

  • Active Users
  • **
  • Posts: 85
  • Jonathan de Blok
    • View Profile
And it broke again... licence saying it succesfully served the lic, slaves is not having it.


Can I run a netwerk license server on eachslave so it can authorize it's local slave?  Or will that break something..


2016-11-23, 13:18:24
Reply #3

JCdeBlok

  • Active Users
  • **
  • Posts: 85
  • Jonathan de Blok
    • View Profile
I works on my 'master' from which I clone machine images, but as soon as I make a new image the new one starts getting the mentioned issue.

Do I need to delete any files/keys  before making a clone for the farm?

2016-11-23, 14:31:09
Reply #4

Ryuu

  • Former Corona Team Member
  • Active Users
  • **
  • Posts: 654
  • Michal
    • View Profile
If the cloned machines have identical hardware configuration (including the HDD ID), there may be problem that there are multiple machines requesting license with the same request ID. You can check their IDs in %localappdata%\CoronaRenderer\request-3dsmax.txt

2016-11-23, 17:44:46
Reply #5

JCdeBlok

  • Active Users
  • **
  • Posts: 85
  • Jonathan de Blok
    • View Profile
If the cloned machines have identical hardware configuration (including the HDD ID), there may be problem that there are multiple machines requesting license with the same request ID. You can check their IDs in %localappdata%\CoronaRenderer\request-3dsmax.txt

here are two codes from different machines,

6179AB0E-FD0A-3655-AEFE

6179AB0E-FD0A-2155-5582

They are partially the same, not sure if that's an issue?

What I don't get is how the lic-server says the slave has been successfully given a license, but the slave never gets it en quits listening after a minute.

Does the lic server actually check if it's recieved or does it just assume the slave got it?

2016-11-23, 17:49:55
Reply #6

JCdeBlok

  • Active Users
  • **
  • Posts: 85
  • Jonathan de Blok
    • View Profile
btw.. this setup used to work fine.. maybe it broke updating from 1.4 to 1.5, not sure. I'll check that later.

2016-11-24, 08:54:40
Reply #7

JCdeBlok

  • Active Users
  • **
  • Posts: 85
  • Jonathan de Blok
    • View Profile
I've solved it by running the license server outside of EC2, on my local lan, and have the EC2 slaves look there and now it all seems to works fine.

Thx!