AWS Thinkbox Discussion Forums

Machines not being woken up despite being candidates

Hi,

i just had a few jobs where no Slaves were being started despite them being candidates and not being blacklisted. The jobs were all assigned to the ‘none’ group and the pool called ‘rs’ and have a Machine Limit of 1.
This is from the Pulse log:

2014-12-14 14:44:43: Power Management - Machine Startup: Checking job "gera_TV_prores_reel07_25fps_from_DPX" (548d74650373631a948b93fb) 2014-12-14 14:44:43: Power Management - Machine Startup: Checking slaves in Machine Group "all" 2014-12-14 14:44:43: Power Management - Machine Startup: - only slaves with assigned pool "rs" should be woken up 2014-12-14 14:44:43: Power Management - Machine Startup: - job is not part of a group, any slaves that are included in the 'none' group should be woken up 2014-12-14 14:44:43: Power Management - Machine Startup: - slaves that are candidates to be woken up based on the job's pool, group, and bad slave list: CELL-RS-17,CELL-RS-18,CELL-RS-19,CELL-RS-20,CELL-RS-21,CELL-RS-22,CELL-RS-09,CELL-RS-10,CELL-RS-11,CELL-RS-12,CELL-RS-13,CELL-RS-14,CELL-RS-15,CELL-RS-16,CELL-WS-25 2014-12-14 14:44:43: Power Management - Machine Startup: - checking slave CELL-RS-17 2014-12-14 14:44:43: Power Management - Machine Startup: - slave is not valid because of job's machine limit 2014-12-14 14:44:43: Power Management - Machine Startup: - checking slave CELL-RS-18 2014-12-14 14:44:43: Power Management - Machine Startup: - slave is not valid because of job's machine limit 2014-12-14 14:44:43: Power Management - Machine Startup: - checking slave CELL-RS-19 2014-12-14 14:44:43: Power Management - Machine Startup: - slave is not valid because of job's machine limit 2014-12-14 14:44:43: Power Management - Machine Startup: - checking slave CELL-RS-20 2014-12-14 14:44:43: Power Management - Machine Startup: - slave is not valid because of job's machine limit 2014-12-14 14:44:43: Power Management - Machine Startup: - checking slave CELL-RS-21 2014-12-14 14:44:43: Power Management - Machine Startup: - slave is not valid because of job's machine limit 2014-12-14 14:44:43: Power Management - Machine Startup: - checking slave CELL-RS-22 2014-12-14 14:44:43: Power Management - Machine Startup: - slave is not valid because of job's machine limit 2014-12-14 14:44:43: Power Management - Machine Startup: - checking slave CELL-RS-09 2014-12-14 14:44:43: Power Management - Machine Startup: - slave is not valid because of job's machine limit 2014-12-14 14:44:43: Power Management - Machine Startup: - checking slave CELL-RS-10 2014-12-14 14:44:43: Power Management - Machine Startup: - slave is not valid because of job's machine limit 2014-12-14 14:44:43: Power Management - Machine Startup: - checking slave CELL-RS-11 2014-12-14 14:44:43: Power Management - Machine Startup: - slave is not valid because of job's machine limit 2014-12-14 14:44:43: Power Management - Machine Startup: - checking slave CELL-RS-12 2014-12-14 14:44:43: Power Management - Machine Startup: - slave is not valid because of job's machine limit 2014-12-14 14:44:43: Power Management - Machine Startup: - checking slave CELL-RS-13 2014-12-14 14:44:43: Power Management - Machine Startup: - slave is not valid because of job's machine limit 2014-12-14 14:44:43: Power Management - Machine Startup: - checking slave CELL-RS-14 2014-12-14 14:44:43: Power Management - Machine Startup: - slave is not valid because of job's machine limit 2014-12-14 14:44:43: Power Management - Machine Startup: - checking slave CELL-RS-15 2014-12-14 14:44:43: Power Management - Machine Startup: - slave is not valid because of job's machine limit 2014-12-14 14:44:43: Power Management - Machine Startup: - checking slave CELL-RS-16 2014-12-14 14:44:43: Power Management - Machine Startup: - slave is not valid because of job's machine limit 2014-12-14 14:44:43: Power Management - Machine Startup: - checking slave CELL-WS-25 2014-12-14 14:44:43: Power Management - Machine Startup: - slave is not valid because of job's machine limit 2014-12-14 14:44:43: Power Management - Machine Startup: There are no slaves that need to be woken up at this time

All those machines are also visible in the Slave panel with the Job Candidate Filter being active. A screenshot of the jobs’ Machine Limit settings is attached.
I can see that they are not being woken up due to the jobs’ machine limit. So i see why it doesn’t wake all of them. But it should at least wake up one machine, shouldn’t it?
As soon as i added all the candidates to the Whitelist manually they were woken up and started rendering the different jobs.
Am i missing something here?

Cheers,
Holger

Thanks for reporting this! We discovered a bug in the logic that would result in no slaves being started for a job that has an empty whitelist. We’ll get this fixed for the public release of v7.

Cheers,
Ryan

Privacy | Site terms | Cookie preferences