AWS Thinkbox Discussion Forums

Unable to Modify Pools/Groups on Slaves

Deprecated Deadline 6 Bug Reports
#1

Hi,

We are unable to update/modify Pools and Groups on some slaves on our farm.

This was occuring in Deadline Version: 6.2.0.22 R, but persists in Deadline Version: 6.2.0.24 R
Windows 7 (Slave and Monitor)

In Manage Pools, I’ve tried clearing the slaves and readding, just removing one pool, copying from another slave, but once I hit ok, in all situations the slave pools are not updated. The [] that normally show up around changing pools don’t show up either.

The same thing happens with Manage Groups on the same slaves. So far I’ve noticed this happening to about 1/30 of our slaves.

Thanks,
Andrea

#2

Can you open up the Console panel in the Monitor and check if there are any error messages? You can find it under View -> New Panel.

Also, is it always the same slaves that are affected, or is it random?

Thanks!
Ryan

#3

Hi,

I’ve checked the console on a few of these occasions and it doesn’t say anything. I don’t know if it would, but the Pulse log also doesn’t show anything. It is always the same slaves.

Thanks,
A

#4

That’s interesting that it’s always the same slaves. Is it possible that there is a version mismatch on these machines? You can check the version column in the slave list in the Monitor.

Another thing you could try is reinstalling the client on these slave machines to see if that helps. If that doesn’t work, it might help if we get your slave states/settings from the database. We can give you the instructions to do that if it comes to it.

Thanks!
Ryan

#5

Hi,

I spoke with Edwin today on another issue and brought this up. He mentioned a bug where having “Exclude machines in the None Pool” caused this issue. I unchecked those options and now I can update my slave pools/groups.

The slave versions are .24, same as my monitor, so I think the issue was/is just that bug.

Thanks,
A

#6

Strange, I thought we had already squashed that bug in 6.1. I’ll chat with Edwin today about it.

Thanks!
Ryan

#7

So it turns out we only half-fixed this issue. We’ve fixed the other “half” of the problem, and it appears to be working as expected in all cases now. We’ll include the fix in RC2.

Thanks!
Ryan

Privacy | Site terms | Cookie preferences