PipelineFX Forum
Qube! => Jobtypes and Applications => Topic started by: rtaege on May 19, 2010, 03:25:31 PM
-
When I try to network render with Nuke, I get this error show up : ERROR: exit status 1. Does anyone know what this means?
I'm running Qube 5.4.5 / Nuke 6.0X / Win 7 x64.
The render nodes are all running Win XP x86
EDIT:
Well I figured out all the errors were just coming from 2 specific render nodes. The rest of them rendered OK. Not really sure what's so different about these 2 machines though.
-
anything relevant in either the stderr or stdout besides the exit code?
-
Not really, here's what they say.
Stdout:
requesting work for: 270.18
got work: 270:16 - running
INFO: running frame 16 -
INFO: running cmd: "C:/Program Files/Nuke6.0v4/nuke6.0.exe" -t -x -X "Write1" -- "H:/Projects/CC10030_Honda_3DConversion/comps/hondacomp_v20_netwoprkTest.nk" 16,16,1
COMMAND: "C:\WINDOWS\system32\cmd.exe" /C ""C:/Program Files/Nuke6.0v4/nuke6.0.exe" -t -x -X "Write1" -- "H:/Projects/CC10030_Honda_3DConversion/comps/hondacomp_v20_netwoprkTest.nk" 16,16,1"
Nuke 6.0v4, 32 bit, built Apr 8 2010.
Copyright (c) 2010 The Foundry Visionmongers Ltd. All Rights Reserved.
eserved.
ERROR: exit status: 2147483649
Stderr:
requesting work for: 270.18
got work: 270:16 - running
reporting status on work for: 270.18 16 - failed
Not sure how much help that is.
-
You say you're running Nuke 5.4v5, but the error message indicates 6.0v4.
Could it be that these two machines have a different version of Nuke installed, and that's the cause of the error?
-
Original post said I was running QUBE 5.4.5 and Nuke 6.0X ;D
Still not sure what it is, but I have a feeling it's related to the actual machines, both are acting a little wierd, one having network conectivity issues, and the other getting Blue screen of deaths. So it's probably just something on my end