Hey everyone, I’m trying to get Deadline Balancer to launch my EC2 instances. It won’t. Looking at the balancer log I’m seeing this error:
Algorithm (7): Targets:
System.NullReferenceException: Object reference not set to an instance of an object
at Deadline.Balancer.BalancerAlgorithm.ExecuteAlgorithm (System.String& errorMessage) [0x00000] in <filename unknown>:0
Deadline verifies my Amazon cloud configuration.
I’m able to manually launch EC2 instances and have them show up in the Monitor and render.
My balancer is set to primary (it is the only one running) and it has the region set to that of my cloud configuration.
My EC2 instances are ubuntu and I’m running my Monitor and the Balancer on a Mac. I’m also running the .51 version of the beta.
At this point I’ve poured over the documentation and the white paper given to me on this forum and I can’t seem to find that I am doing anything wrong.
I hope someone can help me figure this out as I am very eager to finally have this all working.
Hi,
We found this bug recently in version 50. The default logic the Balancer is using was set to “” instead of “DeafultAlgorithm”. It’s a pretty simple fix.
You’re gonna have to go into the repository and make a copy of the Balancer logic plugin in the balancer folder and give it a new name (including the files inside the folder).
Then open the Monitor and open Repository Options then click on Balancer Settings. It’s going to look like “DefaultAlgorithm” is selected but it’s actually not. This form saves on change so all you have to do is change the algorithm to the new one. That should set the logic properly.
There’s actually an unrelated issue with the Balancer that got solved this morning (I’m pretty sure it didn’t make it into 52). Basically it effects having multiple group mappings. Anything past the first one won’t work.
Thanks for the understanding. Hope this helps. Let me know if you run into any trouble.
Eric
The “CloudPlugin has not yet been initialized” issue should be resolved in the Deadline 7 release build 7.0.0.54. Please test it and let us know if you still see any issues.
It seems to have fixed it… sort of. Every once in a while the Balancer will not reflect the cloud settings. I’m having trouble identifying exactly when/how this happens. Sometimes I can change my cloud settings (change my budget) and the Balancer reflects these changes after a refresh. Other times it shows no budget and no instances. When the balancer does this I can restart the balancer, delete it from the balancer list, change cloud settings, wait a dozen or so minutes, or refresh the balancer but, none of these reliably fix it. Sometimes I just start it and it works. I know this isn’t the most helpful response but that’s what I’m seeing over here. But I can say I’m extremely happy to have it work at all.
Thanks for the report. I’ll be keeping an eye out for this update issue. Is your Balancer running remotely or locally, relative to the location of the repository/database?