[posted to rush.general]

Craig Allison wrote:

Hello!

I've just upgraded a box to Debian 4 and have installed Shake 4.1,  

Rush 102.42a.

The box goes online and picks up jobs fine, it will render the first  

allocated frame no problem and then when it picks up the next, it  

renders the frame and gets Shake exit code 0

but Rush doesn't release the frame and move on.  The box will sit all  

night with status "Run" even though the log shows an exit code of 0.   

When you login to the box it will show 2 Shake processes (1 for each  

cpu) taking 0% CPU.

Any ideas?

Hi Craig,

Hit "All Jobs" to make sure you don't have two jobs running

the same scene and frame range.

It's possible the log you're looking at that shows the frame

as 'exit 0' is not the same log as the one that is running the

frame. A possible situation is if there are *two* jobs both

running the same shake job and frame range; the stuck job's

log getting overwritten by the other job that successfully

ran on a different machine.

If this were the case, the "Jobid" and "Hostname" field of the

'Frames' report wouldn't match the same fields in the header

of the frame log.

Can you include the "Frames" report from irush showing the

frame in the Run state, and the *complete* frame log (including

the headers at the top, and the shake exit message at the bottom)?

-- 

Greg Ercolano, erco@(email surpressed)

Seriss Corporation

Rush Render Queue, http://seriss.com/rush/

Tel: 626-795-5922

Fax: 626-795-5947

Cel: 310-266-8906