Deadline ignoring stub limit?!

RicardoMusch · October 28, 2016, 2:53pm

Hi all,

on nuke renders deadline seems to ignore the stub limit of 2 and doesn’t seem to register nodes that are actually rendering with that stub limit.

Image:
We have 2 render licenses, limit is set to 2, 3 machines are rendering and the “stubs in use” column says only one is.

eamsler · October 28, 2016, 3:20pm

This was an issue back in older versions of 7. Which version of Deadline are you on? Would you be able to upgrade?

RicardoMusch · October 28, 2016, 3:33pm

We are on the latest 8.

8.0.10.4

dwallbridge · October 28, 2016, 6:50pm

Hello,

We are seeing this a few times lately, with the negative stub count. Can you verify how long this has been going on for? If the issue existed before upgrading to 8.0.10, you may need to delete and recreate these limits. If you can give this a try and let us know how it goes? Thanks.

RicardoMusch · October 29, 2016, 11:06am

Actually, this is the first time I have seen negative stub limits… its that you pointed it out…

I will try deleting the nuke one and remaking it.

RicardoMusch · November 8, 2016, 3:01pm

To come back to this,

I have re-made loads of the limits, including the Nuke limit, from scratch.

Its still ignoring it and I’m getting more and more (minus) limits.

The limit system seems way more buggy than before.

ryangagnon · November 9, 2016, 3:48pm

Hello,

I’m having some difficulty reproducing this issue, would you be able to provide more information about the conditions in which this problem appears? Are the jobs that are using the offending limits failing often? Are the Limits using overage? Are slaves crashing or stalling prior to the counts being lowered? Can you provide a snapshot of the state of one of the broken limits? You can get this data from mongodb, or you can use the Web Service and request the following in a browser:

http://WEBSERVICEADDRESS:WEBSERVICEPORT/api/limitgroups?Name=LIMITNAME

RicardoMusch · November 11, 2016, 3:31pm

Not using overage
Crashing, no… they error out because they are trying to render a job that the limit is already full for.
The jobs fail because nuke generates errors because the license server tells the extra nodes there are no licenses.
I cannot reach the webservice. (All ports are open)

RicardoMusch · November 11, 2016, 3:33pm

Also, the limits in our version of deadline seem to all have weird problems.

Getting -limits.

RicardoMusch · November 11, 2016, 4:39pm

Continuing this here:
forums.thinkboxsoftware.com/vie … 879#p67879