License fowarder error when launched VIA balancer

Deadline
1

Deadline 10.0.8.1 Release

I have a AWS instance for rendering mental ray. Recently I’ve switched it over to use the UBL, which works well. Whenever I launch my instances from the Cloud window they work and license perfectly. However, when I use balancer to launch the same nodes they will never pick up a job and the nodes will complain that they cannot reach the machine responsible for handling the license forwarding.

I edited the hosts file on the AMI just to make sure there wasn’t an issue there but I can’t think of anything else that could effect this. No change.

Any idea what might be the cause of this?

Thank you,
Bruce

2

Hey Bruce,

Are you using Mental Ray and Deadline UBL? Or just Mental Ray.

If you are using Deadline UBL is the slave an orange color indicating it cannot get a license?

Were you able to get your hands on the slave log when the Slave is not getting licensing. I’d like to see it if possible. Have you checked to see if when the machines are started via the balancer that they have internet access?

Is the license forwarder local or on AWS? Have you looked in the forwarder log for any errors?

Regards,

Charles