AWS Thinkbox Discussion Forums

slave stuck with old pools

Migrating our settings to deadline8, i’ve noticed that some slaves don’t pick up the new pool/group settings they have assigned

Capture.PNG

This slave was restarted a few times. While the slave is offline, the pool/group settings show without the square brackets. As soon as it comes back online and to the idle status, the brackets are back on.

(for future ref, the machine name is lapro0068)

Interesting. Are the lists accurate to what shows up in the configure pools/groups menu, and it’s just adding the brackets on there unnecessarily? If not, what’s off with the list? Is it ordering, pool/group missing, or does it have an extra/old pool/group?

When the slave is offline, it appears to show the good list - and whats displayed for the slave when trying to edit its pools&groups. As soon as it comes back online, it gets the brackets. When remoting into the machine, the slave GUI shows no pools/groups for the slave

Weird. Is it still pulling jobs properly from the pools/groups it’s ‘supposed’ to be assigned to?

Might just be that it’s not reporting them properly in its info object anymore.

Nope, its not picking up anything

Are you guys still getting this issue? We haven’t been able to reproduce this at all internally, and I’m still not sure what would be causing it.

If so, could you get us some logs from a Slave starting up that’s experiencing this?

Haven’t seen this since. It was more obvious during the initial migration, with a fully active farm such issues are hard to notice :\

Privacy | Site terms | Cookie preferences