Could not read/write file type:

Deadline
1

Hi,
Im using Krakatoa to save particles to disk through deadline and after calculating particles for 4 hours, I get this message and the job fails, which causes it to start all over. Any ideas on why this error would occur?

Fred

Error Message
Exception during render: An error occurred in RenderTasks(): RenderTask: Unexpected exception (Exception caught in 3ds max: – Runtime error: Unable to open renderer, possible recursion
not read/write file type:
2009/11/13 13:27:38 ERR: Could not read/write file type:
2009/11/13 13:28:38 ERR: Could not read/write file type:
2009/11/13 13:29:37 ERR: Could not read/write file type:
2009/11/13 13:30:38 ERR: Could not read/write file type:
2009/11/13 13:31:38 ERR: Could not read/write file type:
2009/11/13 13:32:39 ERR: Could not read/write file type:
2009/11/13 13:33:41 ERR: Could not read/write file type:
2009/11/13 13:34:43 ERR: Could not read/write file type:
2009/11/13 13:35:46 ERR: Could not read/write file type:
2009/11/13 13:36:50 ERR: Could not read/write file type:
2009/11/13 13:37:54 ERR: Could not read/write file type:
2009/11/13 13:38:59 ERR: Could not read/write file type:
2009/11/13 13:40:05 ERR: Could not read/write file type:
2009/11/13 13:41:11 ERR: Could not read/write file type:
2009/11/13 13:42:18 ERR: Could not read/write file type:
2009/11/13 13:43:26 ERR: Could not read/write file type:
2009/11/13 13:44:34 ERR: Could not read/write file type:
2009/11/13 13:45:43 ERR: Could not read/write file type:
2009/11/13 13:46:56 ERR: Could not read/write file type:
2009/11/13 13:48:06 ERR: Could not read/write file type:
2009/11/13 13:49:16 ERR: Could not read/write file type:
2009/11/13 13:50:27 ERR: Could not read/write file type:
2009/11/13 13:51:39 ERR: Could not read/write file type:
2009/11/13 13:52:52 ERR: Could not read/write file type:
2009/11/13 13:54:04 ERR: Could not read/write file type:
2009/11/13 13:55:18 ERR: Could not read/write file type:
2009/11/13 13:56:32 ERR: Could not read/write file type:
2009/11/13 13:57:47 ERR: Could not read/write file type:
2009/11/13 13:59:02 ERR: Could not read/write file type:
2009/11/13 14:00:18 ERR: Could not read/write file type:
2009/11/13 14:01:35 ERR: Could not read/write file type:
2009/11/13 14:02:52 ERR: Could not read/write file type:
2009/11/13 14:04:11 ERR: Could not read/write file type:
2009/11/13 14:05:29 ERR: Could not read/write file type:
2009/11/13 14:06:48 ERR: Could not read/write file type:
2009/11/13 14:08:11 ERR: Bad encryption handshake with vendor daemon. Feature: krakatoa-max-render License path: @Durandal; FLEXnet Licensing error:-33,376 For further information, refer to the FLEXnet Licensing End User Guide, available at “www.macrovision.com”.
) (Deadline.Plugins.ScriptPlugin+FailRenderException) (Deadline.Plugins.RenderPluginException)
at Deadline.Plugins.ScriptPlugin.RenderTasks(Int32 startFrame, Int32 endFrame, String& outMessage)

Slave Log
t read/write file type:

2009/11/13 13:37:54 ERR: Could not read/write file type:

2009/11/13 13:38:59 ERR: Could not read/write file type:

2009/11/13 13:40:05 ERR: Could not read/write file type:

2009/11/13 13:41:11 ERR: Could not read/write file type:

2009/11/13 13:42:18 ERR: Could not read/write file type:

2009/11/13 13:43:26 ERR: Could not read/write file type:

2009/11/13 13:44:34 ERR: Could not read/write file type:

2009/11/13 13:45:43 ERR: Could not read/write file type:

2009/11/13 13:46:56 ERR: Could not read/write file type:

2009/11/13 13:48:06 ERR: Could not read/write file type:

2009/11/13 13:49:16 ERR: Could not read/write file type:

2009/11/13 13:50:27 ERR: Could not read/write file type:

2009/11/13 13:51:39 ERR: Could not read/write file type:

2009/11/13 13:52:52 ERR: Could not read/write file type:

2009/11/13 13:54:04 ERR: Could not read/write file type:

2009/11/13 13:55:18 ERR: Could not read/write file type:

2009/11/13 13:56:32 ERR: Could not read/write file type:

2009/11/13 13:57:47 ERR: Could not read/write file type:

2009/11/13 13:59:02 ERR: Could not read/write file type:

2009/11/13 14:00:18 ERR: Could not read/write file type:

2009/11/13 14:01:35 ERR: Could not read/write file type:

2009/11/13 14:02:52 ERR: Could not read/write file type:

2009/11/13 14:04:11 ERR: Could not read/write file type:

2009/11/13 14:05:29 ERR: Could not read/write file type:

2009/11/13 14:06:48 ERR: Could not read/write file type:

2009/11/13 14:08:11 ERR: Bad encryption handshake with vendor daemon. Feature: krakatoa-max-render License path: @Durandal; FLEXnet Licensing error:-33,376 For further information, refer to the FLEXnet Licensing End User Guide, available at “www.macrovision.com”.

) (Deadline.Plugins.ScriptPlugin+FailRenderException) (Deadline.Plugins.RenderPluginException)

at Deadline.Plugins.ScriptPlugin.RenderTasks(Int32 startFrame, Int32 endFrame, String& outMessage)

Error Type
RenderPluginException

Error Stack Trace
at Deadline.Plugins.Plugin.RenderTask(Int32 startFrame, Int32 endFrame)
at Deadline.Slaves.SlaveRenderThread.RenderCurrentTask()

2

Hi Fred,

I am not exactly sure what is causing the problem, but here are some ideas:
*The “possible recursion” message usually means that Krakatoa failed in the previous step and was not closed, so the next frame cannot create another instance of the renderer. In workstation mode, sometimes I have seen Krakatoa failing (due to some memory conditions) and if the RENDER button in the Krakatoa GUI was used, MAXScript catches that as “unknown system exception” and does not let Max go down to desktop, but the Renderer Progress dialog remains open and can never be closed. I suspect that the equivalent situation occurs in Slave mode and the Renderer stays open because it crashed, but not completely. Anyway, it has failed and there is nothing you can do in that case anyway.
*The cannot read/write file message is most probably a side effect of the previous problem.
*Same for the handshake with the license server, I suspect that a more general memory error occurred and all the other messages are side effects of it.
*Of course, the whole could be caused by a license error, in which case the first two errors would be side effects of the last one, but somehow my gut feeling says it was a memory problem.

Now let’s see what you could do to avoid this:

*First of all, the Deadline submission provides two modes - the default one you are using runs each Partition as a Task of a single job using a MAXScript that calls the renderer for the frame range.

*The alternative mode submits one job per partition where the frames are the actual frames to be saved. If you submit your Partitioning Jobs using this method, should the machine crash for some reason, it will not start from the beginning but continue with the next frame. Of course, PFlow being history-dependent, this will cause the restarted frame to preroll all already saved frames, but at least it won’t save them all again (which saves a bit of time). Obviously, in this mode it is a good idea to set the Machine Limit per Job to 1 or 2 because otherwise multiple machines would preroll frames that are already being calculated by the others.

*To provide another level of protection, we allow users of Box #3 to set a Disk Cache in their PFlow and dump the flow to disk as it goes. Krakatoa will modify the path of the Disk Cache in each Partition, so each partition saves both to PRT and to Disk Cache. Should a crash occur, the partitioning would be able to continue much faster because the Disk Cache would provide the particles of the frame before the crash directly from disk without a preroll. This works best with the Task As Job mode since the already successfully saved frames will be marked as Done and won’t even attempt to reprocess.

It would be useful to know whether the crash happens in workstation mode if you run a partition on your local machine instead of submitting to Deadline. Workstation mode uses the same approach and most of the same code as the Partition As Task submission mode, so it would be interesting to know if Krakatoa would crash on the same frame (and why). I assume this is on a 64 bit machine, so I don’t expect it to be lack of memory, but what do I know…

Apropos, on the Beta board we asked all bug reporters to provide Max and Krakatoa version info. Would be good to know.

3

Thanks Bobo,
I’ll look into the disk cache operator since we just bought box3. It would help alot to not have calculate all the way back to where it left off.

Fred