Hey there,
Running Deadline Version: 7.1.2.1 R
Just attempting to work out the best config for our situation;
We have 4 Nuke interactive licenses which we intend to share as workstation and render licenses, however if we send a Nuke job to the farm and limit it to 4 machines, if a user is using one of the licenses then the job will error out due to 1 of the 4 licenses being in use. I have configure the Nuke plugin settings for all nodes to use interactive Nuke licenses.
How would I configure the Nuke plugin so that when it can’t find a license it doesn’t count it truely as a failed/errored task? Or something similar along those lines?
Hello,
I am not sure what to suggest, as the plugin treats a license error as a failure, and I don’t think there is code built in to make it not count it as an actual error, thus adding to the error limits on jobs. I’ll see if I can get a dev to look this over and offer suggestions tomorrow.
Makes sense that it is an error but I guess it is a frustrating one as the issue will resolve, it is not a persistent error…
I had a thought overnight, is there a way to schedule a pool or group?
so;
if Job with pool ‘Nuke’ render only between 9pm - 7am ??
Hi,
@martythinkbox
I need to clarify something here. Are you saying that when a slave picks up a Nuke job and is configured to use an interactive license, which is already in use on that machine, that Nuke fails, but could actually be allowed to continue to render, by piggy-backing of the already checked out interactive license, under that user profile and therefore, we just need to tweak the Nuke plugin code to ignore this edge-case error, which causes the task/job to fail? (in which case, can you provide the full nuke job reports so we can see the Stdout?)
If not and it’s just a case of not having enough licenses, as they are already in use, then without some kind of ability to dynamically query your license server for the current number available and placing some kind of ‘lock’ on it, to ensure it doesn’t get grabbed by anyone else, this is currently not possible to avoid.
However, controlling scheduling is possible via scripting. You could use the house cleaning event (every 60s by default) to check the time of day and edit your nuke limit.
github.com/ThinkboxSoftware/Dea … seCleaning
Ok thanks, it is the second option, so will look at using your script… cheeeers!