Problem with Power Management Groups 5.1.0.46398

Deadline
1

Hello,

We are using Dealine 5.1.0.46398 with 40 dedicated render slaves SINCITY000 to SINCITY039 (i7 970/18Gb/Win XP 64)

I’ve got 2 Power Managment Groups :
RenderFarm_01 (sincity000-sincity006) Idle slaves will be shutdown after 25minutes
RenderFarm_02 (sincity007-sincity039) Idle slaves will be shutdown after 6minutes

I’ve got 1 job with 2 slaves in the white-list (017 and 025)

Here is what I get from Pulse :

[i]Checking job “R&D - Test_3DSMax2011_02” (999_040_002_5bc5aa87)
Checking slaves in Machine Group “RenderFarm_01”

  • job is not part of a pool, any slaves that are included in the ‘none’ pool should be woken up
  • only slaves with assigned group “letruc_all” should be woken up
  • slaves that are candidates to be woken up based on pool and group: Sincity000,Sincity001,Sincity002,Sincity003,Sincity004,Sincity005,Sincity006
  • checking slave Sincity000
    • slave is not valid because of job’s machine limit
  • checking slave Sincity001
    • slave is not valid because of job’s machine limit
  • checking slave Sincity002
    • slave is not valid because of job’s machine limit
  • checking slave Sincity003
    • slave is not valid because of job’s machine limit
  • checking slave Sincity004
    • slave is not valid because of job’s machine limit
  • checking slave Sincity005
    • slave is not valid because of job’s machine limit
  • checking slave Sincity006
    • slave is not valid because of job’s machine limit
      Checking slaves in Machine Group “RenderFarm_02”
  • job is not part of a pool, any slaves that are included in the ‘none’ pool should be woken up
  • only slaves with assigned group “letruc_all” should be woken up
  • slaves that are candidates to be woken up based on pool and group: Sincity000,Sincity001,Sincity002,Sincity003,Sincity004,Sincity005,Sincity006
  • checking slave Sincity000
    • slave is not valid because of job’s machine limit
  • checking slave Sincity001
    • slave is not valid because of job’s machine limit
  • checking slave Sincity002
    • slave is not valid because of job’s machine limit
  • checking slave Sincity003
    • slave is not valid because of job’s machine limit
  • checking slave Sincity004
    • slave is not valid because of job’s machine limit
  • checking slave Sincity005
    • slave is not valid because of job’s machine limit
  • checking slave Sincity006
    • slave is not valid because of job’s machine limit[/i]

Repository consider that both power management group are identical ???!!! Very strange and annoying :slight_smile:

When I add 017 and 025 to RenderFarm_01, they both woke up on Power Management Check.

It’s only a problem with blacklist and white-list because same job without black or white list woke up all slaves

I think I’ve got another strange issue with Management Group, but I need to test something before posting.

2

it doesn’t work correctly when not using black or white list.

Pulse use only settings form RenderFarm_01 power management group (Idle slaves will be shutdown after 25minutes) and not 6min for RenderFarm_02

3

This looks like an issue that we’ve fixed internally already. This fix will actually be included in the beta version I referred to in another thread. It looks like we’ll be able to get the beta out this week.

Cheers,

  • Ryan