Disable jobs that have no licence

[markeljfp]

Greeting Knights

I have encountered the following scenario

Scenario:
•    Artist sends job that has a NukeX node (e.g.: camera tracker).
•    We don’t have licences for NukeX for the farm (barely have enough for the artists!)
•    This causes a licence fail on the farm
•    RR decrements the “licences available” count temporarily
o    It decrements by one, but the requests are quick, so the total drops fast
•    Eventually, with sixty failures in quick succession, the farm grinds to a halt.
o    About an hour later, RR starts incrementing its count and “tests the waters”
o    This behaviour can be manually overridden and accelerated.

Is there a "permanentErrorLine" parameter or similar that will disable the entire job that can be inserted into the config?

We need this behaviour to stop destroying the farm. So when it occurs, just kill the job completely rather than packet by packet.

Hope someone can help!

markel

[RR, Schoenberger]

 

Ah, thanks for the detailed description.

I did not know why the license counter was not working before on your side.

So the issue was not the license counter, the issue is the different license type.

(NukeX is available with interactive licenses only, isn’t t?)

 

I have a different proposal that worked before with Nuke.

If an artist uses for example Sapphire, Reelsmart or pgBokeh Nodes, then RR counts them seperately.

 

We can implement that for NukeX nodes as well.

There is an update planed this week, we just need a list of NukeX node names to add and can paste them into our Nuke submitter.

(Do you use your own Nuke submitter? )

Then you can set „Nuke“ licenses to e.g. 20 and „Nuke- feature NukeX“ to 0.

 

 

 

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

--
If you reply, the message is send to the user group which is sufficient and desired.
("Reply All" might send the message twice to the last author which is not required.
Replying "in private" prevents other users to see the answers and might not be seen by the single receiver if he has email rules in place.
If you want to talk to us in private, please use support@RoyalRender instead)
---
You received this message because you are subscribed to the Google Groups "Royal Render Knights Tavern" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rrKnights+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rrKnights/f1b4dbf9-68ad-4e7b-94ae-958fa30a0ae9n%40googlegroups.com.

[RR, Schoenberger]

Please specify the nodes that the artist has used.
Then I can confirm that we have added them.

[markeljfp]

That sounds great, I will consult with my colleagues to get that list.

Cheers!

markel

[markeljfp]

Hi

The two most common appear to be Furnace (FReGrain) and CameraTracker

From one of our artists:

I have a suspicion all the Furnace plugins are wreaking havoc, FReGrain certainly did in one of my comps https://learn.foundry.com/nuke/content/reference_guide/furnacecore_nodes/fc_nukex.html

so i did a bit of digging, one of the culprits is definitely F_ReGrain, which would mean the whole Furnace suite which I linked to above.

The only other thing I could see in the other two scripts that might be causing the issue is CameraTracker

I hope that is enough information, if not, please let me know!

Cheers and have a good weekend.

markel

[RR, Schoenberger]

 

Thanks, I will add them to the  update today.
And I have requested a full list from Foundry, which will be added to the second next RR update.

[RR, Schoenberger]

Hmm, according to the Foundry support, Nuke render licenses should support NukeX…
Do you know which licenses you have on the farm?

 

„Nuke Render licenses can be used to render files from commercial versions of Nuke, NukeX, Nuke Studio and Hiero. More information can be found here: https://www.foundry.com/products/nuke-family/faqs „

 

 

So far RR had enabled interactive licenses for machine learning only (CopyCat).
But as it seems you are not submitting special Copycat jobs to the farm.

 

 

And a full list of NukeX nodes:

https://learn.foundry.com/nuke/content/comp_environment/nukex/nukex_intro.html