nuke rendering on farm missing plugins on central location

Deadline
1

Have trouble renderding Nuke jobs on the farm using a shared scripts location.
Nuke 9.0 v6
Deadline v7.1
Windows 7 environment

On all machines
NUKE_PATH: Y:\3D\NUKE_SHARED

If I create a simple nuke script using a node from our shared location, it will render on the local workstation, it will render on the farm machine locally, but once the job gets submitted to that farm machine it fails with this error

Error: [18:19.47] ERROR: J_3Way1: ‘J_3Way’: unknown command. This is most likely from a corrupt .nk file, or from a missing or unlicensed plug-in. Can’t render from that Node.
at Deadline.Plugins.ScriptPlugin.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)

[code]=======================================================
Type

RenderPluginException

=======================================================
Stack Trace

at Deadline.Plugins.Plugin.RenderTask(String taskId, Int32 startFrame, Int32 endFrame)
at Deadline.Slaves.SlaveRenderThread.a(TaskLogWriter A_0)

=======================================================
Log

2015-06-02 18:19:45: BEGIN - RENDER04\render
2015-06-02 18:19:45: 0: Start Job timeout is disabled.
2015-06-02 18:19:45: 0: Task timeout is disabled.
2015-06-02 18:19:45: 0: Loaded job: test2.nk (556de57c04b6611fa8006b9f)
2015-06-02 18:19:45: 0: INFO: Executing plugin script C:\Users\render\AppData\Local\Thinkbox\Deadline7\slave\render04\plugins\556de57c04b6611fa8006b9f\Nuke.py
2015-06-02 18:19:45: 0: INFO: About: Nuke Plugin for Deadline
2015-06-02 18:19:45: 0: INFO: The job’s environment will be merged with the current environment before rendering
2015-06-02 18:19:45: 0: INFO: Prepping OFX cache
2015-06-02 18:19:45: 0: INFO: Checking Nuke temp path: C:\Users\render\AppData\Local\Temp\nuke
2015-06-02 18:19:45: 0: INFO: Path already exists
2015-06-02 18:19:45: 0: INFO: OFX cache prepped
2015-06-02 18:19:45: 0: INFO: Starting monitored managed process Nuke
2015-06-02 18:19:45: 0: INFO: Stdout Handling Enabled: True
2015-06-02 18:19:45: 0: INFO: Popup Handling Enabled: True
2015-06-02 18:19:45: 0: INFO: QT Popup Handling Enabled: False
2015-06-02 18:19:45: 0: INFO: WindowsForms10.Window.8.app.* Popup Handling Enabled: False
2015-06-02 18:19:45: 0: INFO: Using Process Tree: True
2015-06-02 18:19:45: 0: INFO: Hiding DOS Window: True
2015-06-02 18:19:45: 0: INFO: Creating New Console: False
2015-06-02 18:19:45: 0: INFO: Running as user: render
2015-06-02 18:19:46: 0: INFO: Executable: “C:/Program Files/Nuke9.0v6/Nuke9.0.exe”
2015-06-02 18:19:46: 0: INFO: Argument: -V 2 -t “C:\Users\render\AppData\Local\Thinkbox\Deadline7\slave\render04\jobsData\556de57c04b6611fa8006b9f\thread0_tempVg5C70\test2.nk”
2015-06-02 18:19:46: 0: INFO: Startup Directory: “C:\Program Files\Nuke9.0v6”
2015-06-02 18:19:46: 0: INFO: Process Priority: BelowNormal
2015-06-02 18:19:46: 0: INFO: Process Affinity: default
2015-06-02 18:19:46: 0: INFO: Process is now running
2015-06-02 18:19:46: 0: Plugin rendering frame(s): 1-2
2015-06-02 18:19:47: 0: INFO: Rendering all enabled write nodes
2015-06-02 18:19:47: 0: STDOUT: Nuke 9.0v6, 64 bit, built May 27 2015.
2015-06-02 18:19:47: 0: STDOUT: Copyright © 2015 The Foundry Visionmongers Ltd. All Rights Reserved.
2015-06-02 18:19:47: 0: STDOUT: Loading C:/Program Files/Nuke9.0v6/plugins/_pathsetup.py
2015-06-02 18:19:47: 0: STDOUT: Loading C:/Program Files/Nuke9.0v6/plugins/init.tcl
2015-06-02 18:19:47: 0: STDOUT: Loading C:/Program Files/Nuke9.0v6/plugins/init.py
2015-06-02 18:19:47: 0: STDOUT: Loading C:/Program Files/Nuke9.0v6/plugins/setenv.tcl
2015-06-02 18:19:47: 0: STDOUT: Loading C:/Program Files/Nuke9.0v6/plugins/formats.tcl
2015-06-02 18:19:47: 0: STDOUT: Loading C:/Program Files/Nuke9.0v6/plugins/getenv.tcl
2015-06-02 18:19:47: 0: STDOUT: Loading C:/Program Files/Nuke9.0v6/plugins/jpgReader.tcl
2015-06-02 18:19:47: 0: STDOUT: Loading C:/Program Files/Nuke9.0v6/plugins/jpegReader.dll
2015-06-02 18:19:47: 0: STDOUT: Loading C:/Program Files/Nuke9.0v6/plugins/jpegWriter.dll
2015-06-02 18:19:47: 0: STDOUT: Loading C:/Program Files/Nuke9.0v6/plugins/Grade.dll
2015-06-02 18:19:47: 0: STDOUT: Loading C:/Program Files/Nuke9.0v6/plugins/exrReader.dll
2015-06-02 18:19:47: 0: STDOUT: [18:19:47 GMT Daylight Time] Read nuke script: C:/Users/render/AppData/Local/Thinkbox/Deadline7/slave/render04/jobsData/556de57c04b6611fa8006b9f/thread0_tempVg5C70/test2.nk
2015-06-02 18:19:47: 0: STDOUT: [18:19.47] ERROR: J_3Way1: ‘J_3Way’: unknown command. This is most likely from a corrupt .nk file, or from a missing or unlicensed plug-in. Can’t render from that Node.
[/code]

What are we missing?

2

Hi,

If you right-click the Nuke job in Deadline Monitor, “Modify Job Properties…” and enter an env variable in this section:
docs.thinkboxsoftware.com/produc … nvironment

such as:

KEY=NUKE_PATH
VALUE=Y:\3D\NUKE_SHARED

and re-queue the job, does it then work ok? I should also ask, when you tested locally on your farm machine, were you logged in using the same user account that the farm uses? (“render”)

3

Hi Mike,
yes that did work, which is great.

But I don’t really want to add a env every time someone submits a job from within nuke.

Can we add it as a default?

4

Great. The strange thing is that the env variable: “NUKE_PATH” if configured like you said, on your render node should just be working.

Can you double-check it’s present under “System variables”, which is under “Computer” --> right-click “Properties” --> “Advanced system settings” --> “Environment Variables…”?

Is it possible, that it was recently added to this machine and this machine hasn’t been restarted since? For example, in a command prompt, if you type “set” without the quotations, is this variable listed? This might just be a case of needing to log-off/log back on again or restart the machine?

5

Hi,
The NUKE_PATH is definitely configured in the ENV variables.

Having said that it has been added, but not restarted. The variable isn’t listed when you type ‘set’ at a prompt. I’ll restart the boxes and see what happens.
Thanks fro your help

6

A restart has fixed it. Thank you Mike.

7

No problem!