AWS Thinkbox Discussion Forums

Best deadline setup for Nuke?

Hello everyone!

I’m quiet new to working with Deadline and wanted to know what would be the proper/best way to have Nuke work with deadline.
I’m a systems assistant at a campus where we have some 30-odd machines and a lot of different people passing through on each machine and a lot of them using Nuke.

Currently I have the repository setup and working on an SMB share and I’ve also moved the .nuke folder to our main work/file SMB share so the plugins can be centralized.

I just did this setting the “HOME” environment variable.

It seems to have worked OK, I installed the deadline submitter and pointed it to the .nuke folder on the work SMB and after the one install all machines had the deadline submitter installed.

I do still have a few problems; like I can’t make a submission from Nuke actually work, it just errors out with the error:
Error: Monitored managed process “Nuke” has exited or been terminated.

I’ve included the .zip file from one of the last attempted archived jobs aswell as pasted the full report from one of the errors below. I think it was the same error both times. They are all the same just that they keep on coming in presumably as deadline tries to make it work and continues to fail at it.

I also foresaw this other “problem”, but since all machines get their preferences from one place now all the layouts in nuke are the same. Is there a way of changing where nuke gets its layout preferences from or is that all baked into the “HOME” path?

Thank you so much for your time, apologies for the beginner questions.

Best regards

–Report paste–

Error

Error: Monitored managed process “Nuke” has exited or been terminated.
ved Deadline.Plugins.PluginWrapper.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)

=======================================================
Type

RenderPluginException

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

ved Deadline.Plugins.SandboxedPlugin.d(DeadlineMessage aqi)
ved Deadline.Plugins.SandboxedPlugin.RenderTask(String taskId, Int32 startFrame, Int32 endFrame)
ved Deadline.Slaves.SlaveRenderThread.c(TaskLogWriter aha)

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

2018-03-06 09.53.21: 0: Loading Job’s Plugin timeout is Disabled
2018-03-06 09.53.23: 0: Executing plugin command of type ‘Sync Files for Job’
2018-03-06 09.53.23: 0: All job files are already synchronized
2018-03-06 09.53.23: 0: Synchronizing Plugin Nuke from \10.128.64.14\DeadlineRepository10\plugins\Nuke took: 0 seconds
2018-03-06 09.53.23: 0: Done executing plugin command of type ‘Sync Files for Job’
2018-03-06 09.53.23: 0: Executing plugin command of type ‘Initialize Plugin’
2018-03-06 09.53.25: 0: INFO: Executing plugin script ‘C:\Users\ftvs\AppData\Local\Thinkbox\Deadline10\slave\ftvs-206-07\plugins\5a9e56ff38c10d30d0ad9949\Nuke.py’
2018-03-06 09.53.25: 0: INFO: About: Nuke Plugin for Deadline
2018-03-06 09.53.25: 0: INFO: Render Job As User disabled, running as current user ‘ftvs’
2018-03-06 09.53.25: 0: INFO: The job’s environment will be merged with the current environment before rendering
2018-03-06 09.53.25: 0: Done executing plugin command of type ‘Initialize Plugin’
2018-03-06 09.53.25: 0: Start Job timeout is disabled.
2018-03-06 09.53.25: 0: Task timeout is disabled.
2018-03-06 09.53.25: 0: Loaded job: deadlinetest.nk (5a9e56ff38c10d30d0ad9949)
2018-03-06 09.53.25: 0: Executing plugin command of type ‘Start Job’
2018-03-06 09.53.25: 0: INFO: Executing global asset transfer preload script ‘C:\Users\ftvs\AppData\Local\Thinkbox\Deadline10\slave\ftvs-206-07\plugins\5a9e56ff38c10d30d0ad9949\GlobalAssetTransferPreLoad.py’
2018-03-06 09.53.25: 0: INFO: Looking for AWS Portal File Transfer…
2018-03-06 09.53.25: 0: INFO: Looking for File Transfer controller in C:/Program Files/Thinkbox/S3BackedCache/bin/task.py…
2018-03-06 09.53.25: 0: INFO: Could not find AWS Portal File Transfer.
2018-03-06 09.53.25: 0: INFO: AWS Portal File Transfer is not installed on the system.
2018-03-06 09.53.25: 0: INFO: Executing global job preload script ‘C:\Users\ftvs\AppData\Local\Thinkbox\Deadline10\slave\ftvs-206-07\plugins\5a9e56ff38c10d30d0ad9949\GlobalJobPreLoad.py’
2018-03-06 09.53.25: 0: INFO: Looking for AWS Portal File Transfer…
2018-03-06 09.53.25: 0: INFO: Looking for File Transfer controller in C:/Program Files/Thinkbox/S3BackedCache/bin/task.py…
2018-03-06 09.53.25: 0: INFO: Could not find AWS Portal File Transfer.
2018-03-06 09.53.25: 0: INFO: AWS Portal File Transfer is not installed on the system.
2018-03-06 09.53.25: 0: INFO: Prepping OFX cache
2018-03-06 09.53.25: 0: INFO: Checking Nuke temp path: C:\Users\ftvs\AppData\Local\Temp\nuke
2018-03-06 09.53.25: 0: INFO: Path already exists
2018-03-06 09.53.25: 0: INFO: OFX cache prepped
2018-03-06 09.53.25: 0: INFO: Starting monitored managed process Nuke
2018-03-06 09.53.25: 0: INFO: Enable Path Mapping: True
2018-03-06 09.53.27: 0: INFO: Stdout Redirection Enabled: True
2018-03-06 09.53.27: 0: INFO: Stdout Handling Enabled: True
2018-03-06 09.53.27: 0: INFO: Popup Handling Enabled: True
2018-03-06 09.53.27: 0: INFO: QT Popup Handling Enabled: False
2018-03-06 09.53.27: 0: INFO: WindowsForms10.Window.8.app.* Popup Handling Enabled: False
2018-03-06 09.53.27: 0: INFO: Using Process Tree: True
2018-03-06 09.53.27: 0: INFO: Hiding DOS Window: True
2018-03-06 09.53.27: 0: INFO: Creating New Console: False
2018-03-06 09.53.27: 0: INFO: Running as user: ftvs
2018-03-06 09.53.27: 0: INFO: Executable: “C:\Program Files\Nuke11.1v1\Nuke11.1.exe”
2018-03-06 09.53.27: 0: INFO: Argument: -V 2 -t “C:\Users\ftvs\AppData\Local\Thinkbox\Deadline10\slave\ftvs-206-07\jobsData\5a9e56ff38c10d30d0ad9949\thread0_tempKbS8F0\deadlinetest.nk”
2018-03-06 09.53.27: 0: INFO: Full Command: “C:\Program Files\Nuke11.1v1\Nuke11.1.exe” -V 2 -t “C:\Users\ftvs\AppData\Local\Thinkbox\Deadline10\slave\ftvs-206-07\jobsData\5a9e56ff38c10d30d0ad9949\thread0_tempKbS8F0\deadlinetest.nk”
2018-03-06 09.53.27: 0: INFO: Startup Directory: “C:\Program Files\Nuke11.1v1”
2018-03-06 09.53.27: 0: INFO: Process Priority: BelowNormal
2018-03-06 09.53.27: 0: INFO: Process Affinity: default
2018-03-06 09.53.27: 0: INFO: Process is now running
2018-03-06 09.53.27: 0: Done executing plugin command of type ‘Start Job’
2018-03-06 09.53.27: 0: Plugin rendering frame(s): 0-32
2018-03-06 09.53.27: 0: Executing plugin command of type ‘Render Task’
2018-03-06 09.53.27: 0: INFO: Rendering all enabled write nodes
2018-03-06 09.53.28: 0: STDOUT: Nuke 11.1v1, 64 bit, built Dec 7 2017.
2018-03-06 09.53.28: 0: STDOUT: Copyright © 2017 The Foundry Visionmongers Ltd. All Rights Reserved.
2018-03-06 09.53.34: 0: STDOUT: FOUNDRY LICENSE ERROR REPORT
2018-03-06 09.53.34: 0: STDOUT: ----------------------------
2018-03-06 09.53.34: 0: STDOUT: Timestamp: Tue Mar 6 09:53:34 2018
2018-03-06 09.53.34: 0: STDOUT: License(s) Requested:
2018-03-06 09.53.34: 0: STDOUT: nuke 2017.1207 render only with options all
2018-03-06 09.53.34: 0: STDOUT: Extended Info: None Provided
2018-03-06 09.53.34: 0: STDOUT: Host : ftvs-206-07
2018-03-06 09.53.34: 0: STDOUT: System ID(s) : a0369f3f3914 , a0369f3f3916 , 0023dfdf1046 , 0023dfdf229a
2018-03-06 09.53.34: 0: STDOUT: RLM Environment Info: C:\Users\ftvs\FoundryLicensing\a0369f3f3914;C:\Program Files\The Foundry\RLM;C:\ProgramData\The Foundry\RLM;C:\Program Files (x86)\The Foundry\RLM;C:\Users\ftvs\FoundryLicensing
2018-03-06 09.53.34: 0: STDOUT: Reason for failure: No such feature found.
2018-03-06 09.53.34: 0: STDOUT: RLM LICENSE DIAGNOSTICS
2018-03-06 09.53.34: 0: STDOUT: ---------------------------
2018-03-06 09.53.34: 0: STDOUT: nuke_r : License server does not support this product (-18)
2018-03-06 09.53.34: 0: STDOUT: License Path:
2018-03-06 09.53.34: 0: STDOUT: C:\Users\ftvs\FoundryLicensing\a0369f3f3914;C:\Program Files\The Foundry\RLM;C:\ProgramData\The Foundry\RLM;C:\Program Files (x86)\The Foundry\RLM;C:\Users\ftvs\FoundryLicensing;C:\ProgramData\The Foundry\RLM
2018-03-06 09:53:34: 0: WARNING: Monitored managed process Nuke is no longer running
2018-03-06 09:53:34: 0: Done executing plugin command of type ‘Render Task’
eikmar16__Nuke__jo070_comp_main_markusE_v009.n__5a9a9b26c5182131707cd633.zip (75.5 KB)

2018-03-06 09.53.34: 0: STDOUT: nuke_r : License server does not support this product (-18)

Do you have a license for nuke render? If not you could try running nuke as interactive

docs.thinkboxsoftware.com/produ … figuration

Just an FYI here, the error “Error: Monitored managed process ‘X’ has exited or been terminated.” means that the program closed without us asking it to, which can be a bunch of different reasons (crash, no license, someone went and killed it for fun). In normal operation for batch-mode plugins, we’ll ask the application to close.

Ant’s right though, looks like you don’t have any render licenses for Nuke (in fact, the license server doesn’t seem to have a single one). You can try burning workstation licenses by configuring a set of machines to use interactive licenses when they pick up a job:

You’ll find that fancy window in the “Tools” menu when you’ve enabled “Super User Mode” under “Configure Plugins”.

I thank you very much for your wisdom and help. I was not aware that workstation licenses and rendering licenses were not the same/seamlessly interchangeable. Worked by just adding machines to the interactive license list.

As for the plugin path for nuke, is there another environment variable used to set only that? I see that the HOME variable is a global variable used by a few other programs, notably Houdini

Thank you again for your help so far!

Not sure, but a quick Googling of “Nuke Environment Variables” (sans quotes) brought this up:
help.thefoundry.co.uk/nuke/cont … ables.html

Same thing for “Nuke Plugin Path” found this guy:
help.thefoundry.co.uk/nuke/cont … _path.html

On the Deadline side, there are a few ways to set those but my preference has always been to configure it outside of Deadline at the OS-level so that you can test render problems outside of the normal render pipeline:
docs.thinkboxsoftware.com/produ … m-deadline

Well once again I bow, thank you very much for your help.

Now I’ll go be embarrased for not being able to google this forth by myself :blush:

Thank you again for all the help! :mrgreen:

You’re quite welcome! It’s still nice to have some initial questions handled here for the next person. :slight_smile:

Also, I’ve opened a dev issue so we catch and throw a specific error on licensing errors for future generations.

Privacy | Site terms | Cookie preferences