Nuke plugin errors

[Berkyjay]

Hi all, we are trying to get Peregrine’s Bokeh plugin working on the farm and it seems to be having some issues. I’ve been working with Peregrine to track down the issue but I’d thought I would ask around here as well. So locally everything runs great. We have the RLM server running on a virtual machine and we set the environment variables on all of our machines…no issues. But when I try to run a job through Deadline it seems like the slaves have issues accessing the license server. I’m running the tests on my user machine and I have it set to run in interactive mode, but it always says that no valid license has been found. I’m wondering if the way Deadline ruins Nuke is preventing the slave from seeing the license server. It’s just a shot in the dark kind of idea.

James
Bokeh_debug_01.txt (9.45 KB)

[Berkyjay]

OK so I heard back from Peregrine support and this was their response:

When you submit a job to the farm Deadline takes control over the environment (and user) that the job is run as, so even if you’ve set peregrinel_LICENSE on your workstation this doesn’t guarantee that Deadline will use this. I know from other customers using Deadline with Bokeh you have a specific configuration file that can be used to push environment variables to the Deadline machines and this is how they’re setting the peregrinel_LICENSE variable.

So my question is, does this config file exist already or is it a custom file that I need to establish myself?

[Berkyjay]

I was able to figure out my issue from another thread dealing with env variables. I basically added this line to SubmitNukeToDeadline.py:

pgBokeh_ENV = '7070@rlm' fileHandle.write( "EnvironmentKeyValue0=PEREGRINEL_LICENSE=%s\n" % pgBokeh_ENV )

[dwallbridge]

Hello James,

Sorry for not seeing this earlier. I am glad they were able to get you down the right path for this solution, and that it should be easy to just set it for the farm in that one change. Hopefully others will find this if they have the same problem.