[D8] NUKE - Limits being ignored [UNSOLVED]

Deadline
1

Hi Guys,

my limit is still being ignored by Nuke.

I’ve added the “required limit” → “nuke” (limit)

Have set it to 2 for license limit purpose.
(Since upgrading I re-made the limit)

Deadline 8.0.10.4

2

This only happens on Nuke. All other limits work the same way and seem to work/limit licenses correctly.

3

Are there any other jobs running with Nuke that don’t have the limit selected?

You can always use the web interface on RLM to see where the licenses are going.

Did you give it a little bit of time to take in the command, I think there can be a wait to propagate the command.

4

Nuke Limit Webservice output

{“Props”:{“Limit”:2,“Overage”:0,“RelPer”:0.0,“Slaves”:[],“White”:false,“SlavesEx”:[],“ThreePLE”:null,“UseThreePLE”:false,“ThreePLPC”:false,“UnLmt”:false},“Name”:“nuke”,“Holds”:[],“Used”:0,“InOverage”:0,“StubLevel”:2,“Type”:0,"_id":“nuke”}

EDIT
Two machines will render, its just that the other machines ignore the limit and will try to render as well.
This generates an error and eventually the job fails because of too many errors.
Normally (although now I’m not sure the limit system actually works correctly) other machines will not pick up the job if the limit has been reached.

5

So I’ve added a bunch of Limits with various settings into the nuke Plugin and they still don’t work.

The limit list is never up to date with the actual machines rendering or trying to render the multiple jobs.

nukelimits.PNG
nukelimits.PNG1083×635 41.5 KB

6

Removed all Nuke Limits, remade a limit using “Slave” usage limit instead of machine.

Seems to work.

The Machine Usage Limit seems to be ignored by any Nuke Jobs. Or not work.

7

Hey Ricardo. We did find a bug recently where an existing limit could get a negative count which I’m sure is what was causing this offset for you. The problem with the fix is that it didn’t correct the limit, so re-creating it was required. Did you use a version of 8.0 prior to service pack 10?

8

Actually, my problem is not fixed, its back. :frowning:

Yes we did, I have recreated the limits though. It still wont work.

All other limits (apart from the negative limits problem, which is present after recreating them too) seem to work fine, and just Nuke seems to ignore the limit…

9

Hey Ricardo,

Could you get me a dump of your database? It should show off what’s going on with the configuration of your farm. Please send that direct to support@thinkboxsoftware.com. You can make a dump by running this in a command prompt:

c:\DeadlineDatabase8\mongo\application\bin\mongodump --port=27080
explorer .

If you want to strip it down, I’m most interested in your limits and plugin configuration for Nuke so you can delete the “jobs” json file. I’m curious if there are problems relating to node locked licenses.

10

Emailed you!

:slight_smile:

11

Okay! Got it and did some investigating.

It turns out you’re hitting a known issue with a negative “InOverage” number. We’re currently working on it, so I’ll see if I can get some details. It’s great to have more data on the situation.

12

Situation:

2 Nuke render Floating Licenses
3 Nuke Interactive Floating Licenses

Farm machines (around 40 ish, 24 licenses)

Limits config:
Nuke Limit (machine or slave does the same)
limit: 2
No blacklist/whitelist
Machines excluded from limit: 3 machines (these are the machines the nuke artists use, to have more renders going using the interactive licenses)

Nuke Plugin Config:
machine that can use interactive license: (the 3 machines that are used by Nuke Artists)

13

Well, after more investigating it looks like there is some logic we need to play with, but it would be good to get more data.

Would you be willing to re-create a machine-limit version so we can get a dump of that? Also, any other tips we could use to try a re-create here? I guessed concurrent tasks might help, but that doesn’t seem like it’s the problem here… Maybe it’s because the limit is so small?

14

Hey, these are already new as I read that you had problems with minus limits.

So These limits where made in Deadline 8.0.10.4 yesterday.

15

Hey, for the moment my solution is to make my nuke jobs dependent of each other and to manually set the limit of machines but I can’t keep doing this and I really can’t see why only Deadline Nuke jobs seem to have this problem.
Altough my other limits also still frequently get negative numbers.

16

Hello,

I will pass this along to Edwin and see if he can add this to the testing workflow he is using to try and fix this.

17

Thanks!

18

Update here: We have some limit checking fixed in SP12 that’s due out this week… I’m hoping it’ll help out with these Nuke limit issues, but on the surface they seem unrelated to what was done. Would you be willing to give the update a shot and report back?

I’ll also see if maybe we can put some extra debug code so we can try catching things, but if you have more than 10 machines it’s going to be a challenge to dig up all the Slave logs.

19

Yeah we can give that a shot!

:slight_smile:

I could limit the nuke renders to specific nodes, if the limit works :stuck_out_tongue:

20

Well, you could technically do that now I suppose… The issue you’re hitting is in the book keeping for who has a limit and who doesn’t so if you wanted to just isolate the limit to a specific set of machines that should work just fine.

I want to discuss some testing ideas with the dev guys for limits… Right now it’s a very hard system to troubleshoot.