Deadline 6 slaves crashing

I spoke with Edwin about this last week and I said I’d try to send along information when I was experiencing these crashes. This is all of the info I could find. I took a screen grab of the window that popped up about the crash. I am also including the log from C:\ProgramData\Thinkbox\Deadline6\logs. If there is anymore info I can get please let me know. Also, I had another machine crash at the same time.


deadlineslave_RENDER03-RENDER03-2013-11-04-0000.log (338 KB)

Here’s the info from another crash. This one acted differently though. Included are the log, a screen grab, and the text from the windows error window.
deadlineslave_RENDER11-RENDER11-2013-11-04-0000.log (785 KB)
Deadline_crash.txt.txt (868 Bytes)
deadline_crash_Image.JPG

Woah! Okay, so it looks like the process output file handle is being closed… And we’re calling it from some thread pool that I’m going to guess is the concurrent render tasks.

Me and Ryan’ll need to spend some time looking at this.

Good news on this one! Turns out Ryan randomly hit this awhile ago.

He ended up fixing that for 6.1 awhile ago.

Are you on the beta? Can you see if it fixes this issue for you?

Hey Edwin, I don’t have 6.1 beta studio wide yet. We’re waiting until we finish up some 911 work. I’m hoping to switch over later this week and then I’ll be able to truly put it through it’s paces.

Hello James,

Just let us know how this works for you once you have had that chance.

Cheers,

Hi guys,

Any update on this potentially rolling out as a 6.0 maintenance patch? I think I’m experiencing the same problem as I am trying to run up to 10-15 concurrent tasks on brand new beefy 32 core 128 GB machines and having random crashing on at least one node almost every time I submit a job. We’re still on version 6.0.0.51561 and I’m running Maya software render jobs submitted via command line. On previous, smaller nodes (8 core, 32GB), I was running 3 concurrent tasks but also still seeing similar issues.

I’ll talk to my IT people about trying 6.1 to see if it fixes but the software has a wide user-base and it may be difficult to convince them to roll out a version upgrade still in beta.

Thanks,

I would say, hang in there and maybe check back here before the end of the month… :wink: