HANGING MACHINES

Deadline
1

I have some random machines on my farm hanging on jobs all the sudden. They go into an infinite rendering state but never produce a frame or timeout with an error. I realize that this is a bit of a general non specific but when I look at the slave log it seemed to be stopped at the starting up stage but there doesn’t seem to be any other data. I would gladly send the log that would help but I am not sure where to get it from in order to send to you guys. Can you let me know what I should do here?

Thanks.

2

If you go to the slave application when it gets stuck, and select Help -> Explore Log Folder, you can find the most recent slave log and post it. It should contain all the info we need up until the slave hangs.

Just a few initial questions:

  1. Does this only happen for specific types of jobs (ie: Maya, Nuke, etc), and if so, is it limited to specific scene files?
  2. If it’s specific to a job type or scene file, does the hang always occur at the same point in the rendering process?

Cheers,

  • Ryan
3

Yeah, It seems that it only hangs on a krakatoa job, whether PRT or rendering. I have attached the log file, I couldn’t find anything useful but you might see something that’s wrong.
deadlineslave(Ibm001)-2012-06-28-0001.log (1020 KB)

4

Thanks! The one thing that I noticed for the last two jobs in the log that appeared to hang was that Deadline pressed OK on an error message that popped up:

I wonder if that’s related to the problem. Are you able to open this scene in workstation mode on these machines and render locally?

5

Yeah! That’s the message I keep seeing when the machines are hung up, but I don’t know how to tell what it’s pressing “ok” on. I upgraded to Krakatoa mx from version 1.6 in the last week so I have a feeling that has something to do with it but It doesn’t seem to give any other info on what it’s pressing “ok” on.

6

I’m curious to know if you still see this if you launch Max on the machine manually and try to load the scene. If you do, then at least you can see the error message. It’s definitely starting to sound like a Krakatoa-related problem, so it might be a good idea to post this on the Krakatoa forums too. First though, it would be good to test to see if you get the same error when launching Max manually on one of the slaves.

Cheers,

  • Ryan