Hi
I have a couple of questions, some are general and some Vue specific.
I’m running some Vue test renders on 3 machines. 2 Macs and a PC, one of the Mac’s is the one i submitted the job from and its also a slave. Everything works fine except that Mac slave keeps crashing with no warnings or error messages, its just shuts down. I attached the crash report.
Also how do i know from the monitor where each slave is rendering its frames at? I notice the Macs render the frames at the location specified in the render options in the software while the PCs render locally to the software’s default folder. Maybe its a permissions thing but I’d like to know if there is an easy way in the monitor to find out where the frames ended up.
When one of the slave crashes or has any sort of error is there any setting to let deadline automatically queue those frames to another slave? The way i did it was manually select that task and re-queue it while blacklisting the slave that crashed.
Thanks
mono_2011-10-24-162034_Selim.crash.zip (9.78 KB)
Try downgrading Mono to 2.6.7. We find this is the most stable version of Mono at this point:
download.mono-project.com/archiv … /download/
Version 2.10.6 has recently been released as well:
go-mono.com/mono-downloads/download.html
So you could try upgrading to 2.10.6 first to see if that improves things, and then downgrade to 2.6.7 if it doesn’t.
When it comes to crashes, Deadline would eventually realize the slave has crashed and would automatically mark it as stalled and requeue the task.
For Vue, I’m guessing that because the specified output path isn’t valid on Windows, they just default to a local folder. Unfortunately, Vue doesn’t allow us to control where the output goes from the command line, so Deadline can’t swap out the output path based on the current OS like we do for other applications. Do you know if Vue supports relative paths? If so, then maybe you could place the Vue scene in a network location, and because the output path is relative to it, both Windows and OSX slaves should render to the same folder.
Cheers,
Downgrading to 2.6.7 seems to have fixed the problem. Thanks
I guess copying the files back after the download is done isnt that bad.
Thanks for the help.
Glad to hear that downgrading to 2.6.7 fixed the problem. I think we’re going to change our system requirements documentation to only list 2.6.7 as the supported version of Mono, or at the very least, try to make it more clear that it is the most stable version, because others have had success with the 2.10.x series.
Cheers,