Naiad emp2prt conversion job error

Hello,

Yes, I know it’s dead, but we’re using it a lot, so I though I’d report this :slight_smile: When I try to run the emp2prt conversion job dependency from the naiad submitter, the job errors out with this log:

0: STDOUT: Naiad EMP to PRT Converter
0: STDOUT: Version 0.94
0: STDOUT: Initializing Naiad…
0: STDOUT: Naiad: Scanning C:\Program Files\Exotic Matter\Naiad 0.6.1\server\standard-sig …
0: STDOUT: Naiad: Compiled SIG: Body
0: STDOUT: Naiad: Compiled SIG: Camera
0: STDOUT: Naiad: Compiled SIG: Field-Fire
0: STDOUT: Naiad: Compiled SIG: Field-Gas
0: STDOUT: Naiad: Compiled SIG: Field-Smoke
0: STDOUT: Naiad: Compiled SIG: Field
0: STDOUT: Naiad: Compiled SIG: Mesh
0: STDOUT: Naiad: Compiled SIG: Particle-Liquid
0: STDOUT: Naiad: Compiled SIG: Particle
0: STDOUT: Naiad: Compiled SIG: Rigid-Body
0: STDOUT: Naiad: Compiled SIG: Volume
0: STDOUT: Naiad: Scanning C:\Program Files\Exotic Matter\Naiad 0.6.1\server\user-sig …
0: STDOUT: Naiad: Compiled SIG: NOT-Mesh
0: STDOUT: Naiad: Loaded user body code: NOT-Mesh
0: STDOUT: Parsing command line arguments…
0: STDOUT: Loading EMP file ‘X:/rnd/000/000/rnd_000_000_fx_water-slideoff_hv_v001/particle-liquid_emp/particle-liquid.1001.emp’…
0: STDOUT: Naiad: Reading EMP: X:/rnd/000/000/rnd_000_000_fx_water-slideoff_hv_v001/particle-liquid_emp/particle-liquid.1001.emp
0: STDOUT: (emtimer) : [Body ‘Particle-Liquid’ loaded in 0.00312074 sec]
0: STDOUT: Requesting body ‘Particle-Liquid’ from EMP file ‘X:/rnd/000/000/rnd_000_000_fx_water-slideoff_hv_v001/particle-liquid_emp/particle-liquid.1001.emp’…
0: STDOUT: Body Count in EMP: 1
0: STDOUT: Body Names in EMP:
0: STDOUT: ‘Particle-Liquid’
0: STDOUT: Looking for particle shape in body ‘Particle-Liquid’…
0: STDOUT: Block count: 628
0: STDOUT: Channel Count: 4
0: STDOUT: Channel: 1 / 4 (Saving ‘position’ as: ‘Position’)
0: STDOUT: Channel: 2 / 4 (Saving ‘velocity’ as: ‘Velocity’)
0: STDOUT: Channel: 3 / 4 (Saving ‘droplet’ as: ‘Droplet’)
0: STDOUT: Channel: 4 / 4 (Saving ‘age’ as: ‘Age’)
0: STDOUT: Allocating Memory…
0: STDOUT: Particle Buffer: 1239424 [bytes] (Particle Count: 38732, Particle Size: 32 [bytes])
0: STDOUT: Loading data to memory (embrace yourself): 1/628
0: STDOUT: Loading data to memory (embrace yourself): 2/628
0: INFO: Process exit code: 255
Scheduler Thread - Render Thread 0 threw a major error:

Exception Details
RenderPluginException – Error in CheckExitCode: Renderer returned non-zero error code, 255. Check the log for more information.
at Deadline.Plugins.ScriptPlugin.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)
RenderPluginException.Cause: JobError (2)
RenderPluginException.Level: Major (1)
RenderPluginException.HasSlaveLog: True
Exception.Data: ( )
Exception.TargetSite: Void RenderTask(System.String, Int32, Int32)
Exception.Source: deadline
Exception.HResult: -2146233088
Exception.StackTrace:
at Deadline.Plugins.Plugin.RenderTask(String taskId, Int32 startFrame, Int32 endFrame)
at Deadline.Slaves.SlaveRenderThread.RenderCurrentTask(TaskLogWriter tlw)

Thanks :slight_smile:

Hello Hristo,

So it’s kind of hard to tell what might have happened from the log fragment there. Could I have you grab the render executable and arguments from a full job report and try to run the job from the command line on one of your render nodes, maybe even the same node? We would love to see how the results differ there from the deadline job. Once you’ve done that, can you send the original job report and the output from the command line over in separate files? Thanks.