AWS - Slaves don't join Deadline monitor until restart

Deadline
1

Hi,

It’s starting to quiet down here for Christmas, so I’ve been setting up a new repo with the latest version of Deadline 10.

I’ve reconfigured new AWS instances with the latest Deadline Ami base image and all our software, but they have a little problem where the slaves don’t show up in the Deadline monitor until they are restarted through the AWS Instances console.

I waited 30 minutes for them to show up by themselves, but straight after a manual reboot they joined the monitor.

Any ideas on what I can check on the instance?

Thanks.

2

Is this a Linux or Windows AMI? Did you upgrade Deadline on the AMI or are you using the version that was already installed?

3

It’s a windows AMI, based off Deadline Slave Base Image Windows 10.0.23.3 2018-11-28T194728Z

All I do is just install 3dsmax and corona/vray/itoo stuff, so nothing else has been tweaked.

4

Squeaky:
Probably a stupid question, but did you do the “Shutdown without Sysprep” option when creating your AMI?
https://docs.thinkboxsoftware.com/products/deadline/10.0/1_User%20Manual/manual/aws-custom-ami.html , about 2/3 down the page…

I have a similar custom AMI that is working well (with a different issue – PhoneixFD) as far as booting and running.

5

Hi Jeff,

Yes, they are always done Shutdown without sysprep before imaging.

I’ve still got the AMI as a stopped state, so I’ll fire it up and reimage and see what happens!