So I’ve been testing Draft on the Mac side of our render farm after Nuke jobs, and I just tried running a Maya job from windows. It errored out for not being able to read the path.
Looks like some of my problem (ie. Nuke now works on Windows farm nodes) was solved using this standard substitution info in Deadline (Mapped Path Setup):
Please open \repository\events\Draft\Draft.py with a text editor. Find these lines:[code] scriptArgs += 'inFile="%s" ’ % Path.Combine( outputDirectory, outputFileName )
Auxiliary File #2 ("/pfcluster/Alphaville/PRODUCTION/01_JOYLUCK/2D_PROJECTS/NUKE/PRJ/billg/drafttest.nk")
Events plugin ‘backup’ could not be loaded from the repository because: Could not open event plugin configuration “/Volumes/DeadlineRepository/events/backup/backup.dlinit” because: could not read hashtable file (Deadline.Events.DeadlineEventPluginException)
Result=Success
JobID=003_100_00b_1240fb97
Exception during render: An error occurred in RenderTasks(): Error in CheckExitCode(): Renderer returned non-zero error code, 1. Check the log for more information.
at Deadline.Plugins.ScriptPlugin.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage)
I made this change but it still doesn’t seem to be picking up on windows machines. It seems to come down to whether either the machine that the original job (Maya, Nuke, AE) was submitted to Deadline is OS X or Windows, OR, if the processor that kicks off the Draft job is OS X or Windows. I can’t really tell.
Here’s what I got when an AE job tried to run the Draft post-process (no new Draft jobs kicked off in the queue):
Log Date/Time = Mar 28/12 20:52:04
Frames = (no task)
Slave Machine = (No Slave)
Slave Version = (no slave)
Plugin Name = Draft
My Nuke jobs that kick off in OS X work fine. The Draft group is all Mac farm machines. My Maya jobs run on Windows but then vanish (like above) when they try to run Draft (on OS X). The AE job was kicked off on a Windows machine into the Winfarm group, ie. all windows render nodes.
Not sure how to proceed. Any suggestions on how to troubleshoot stuff like this would be super appreciated.
Paul and I have discussed this, and I think we figured out a solution for this. I’ll need to do a bit of coding for it, but I’ll upload the results here and let you know when I’m done.
In the meantime, I would recommend being careful with the Path Mapping stuff you added in Deadline. The inFile and outFile arguments currently aren’t getting passed through it anyways (though the script file itself should be), and I seem to recall that using our Path Mapping function to map “/pfcluster” to “\pfcluster” would result in triple slashes in some cases for you guys (which could muck up other renders). At least, that’s what I remember from a support thread with Andrew and Drew; just thought I’d give you a heads up
Just wanted to confirm that the changes you made to the other ‘plugin scripts’ that we use, have been implemented for draft. We had to have you adjust the maya, ae, cinema scripts to work, for our pathing setup. let us know if you want me to send an example back to you.
That’s part of what I was looking into here; the scripts I’m attaching to this post (and which will be part of the next Deadline release) should account for that.
Speaking of which, below are the updated scripts I’ve fixed up (four of them). The Draft plugin will now perform Path Mapping swaps on all arguments, as well as make sure paths only start with a single ‘/’ on Linux/OSX (instead of 2). Note that these scripts do not include any changes Paul may have suggested/provided for you guys, so you might have to edit these scripts to re-implement some of those (I haven’t been keeping track of them).
I’ve listed the appropriate location for each of these scripts in their file comments; these are all relative to the Repository’s root path. It’s particularly important that you extract them to the right spot, since there’s two of the zipped files that are named the same (Draft.py), but they go in different spots.
