AWS Thinkbox Discussion Forums

nuke crash - slave hangs

Weird error,… slave seems to handle the nuke crash properly, but never kills nuke:

2013-10-30 11:07:12: 0: STDOUT: [11:07:11 Pacific Daylight Time] Read nuke script: //inferno2/projects/nemo/scenes/HB_118_0970/2d/slapcomps/HB_118_0970_slapcomp_v0010/linear_2karriana/HB_118_0970_slapcomp_v0010_dpo.nk
2013-10-30 11:07:12: 0: STDOUT: Wed Oct 30 11:07:12 2013 (+750ms) :frowning:localizeReads): Localizing nodes…
2013-10-30 11:07:12: 0: STDOUT: Wed Oct 30 11:07:12 2013 (+0ms) :frowning:localizeReads): Disabling localization: Failed to find Write nodes being processed…
2013-10-30 11:07:12: 0: STDOUT: >>> [11:07.12] ERROR: PolyText4: Error opening font: “/Windows/Fonts/ChaparralPro-Regular.otf”
2013-10-30 11:07:12: 0: STDOUT: [11:07.12] ERROR: PolyText3: Error opening font: “/Windows/Fonts/ChaparralPro-Regular.otf”
2013-10-30 11:07:13: 0: STDOUT: Total render time: 0.00 seconds
2013-10-30 11:07:13: 0: STDOUT: Traceback (most recent call last):
2013-10-30 11:07:13: 0: STDOUT: File “stdin”, line 1, in
2013-10-30 11:07:13: 0: STDOUT: RuntimeError: PolyText3: Error opening font: “/Windows/Fonts/ChaparralPro-Regular.otf”
2013-10-30 11:07:14: 0: An exception occurred: Error in RenderTasks: RuntimeError:
2013-10-30 11:07:14: at Deadline.Plugins.ScriptPlugin.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel) (Deadline.Plugins.RenderPluginException)
2013-10-30 11:07:14: 0: Unloading plugin: Nuke
2013-10-30 11:23:00: Listener Thread - ::ffff:172.19.6.114 has connected
2013-10-30 11:23:00: Listener Thread - Received message: StreamLog
2013-10-30 11:23:00: Listener Thread - Responded with: Success

It just shows in the monitor as if it was still rendering, but its been sitting there for 16 mins like that (nuke was an active process on the machine)

(we are not using batch mode)

Are you sure batch mode wasn’t enabled for this job? That’s the only way I could reproduce this problem.

Attached is an updated Nuke.py file that should fix the problem in batch mode.
Nuke.zip (5.1 KB)

Well, this is what i typed first: “Yeah, we disabled batch mode globally after running into some issues (which we are trying to fix now)”.

But turns out, the artist is still using an old version of the configuration from yesterday, when we were trying batch mode… so yep, it was batch mode :slight_smile:

Thanks for the fix!
l

Privacy | Site terms | Cookie preferences