[posted to rush.general]
Craig Allison wrote:
Done 0010 3 render43 4882 render48.62 03/25,17:23:19 00:30:35
Done 0011 3 render43 4884 render48.62 03/25,17:23:19 00:30:35
Done 0012 3 render43 4907 render48.62 03/25,17:53:54 00:00:17
Done 0013 3 render43 4909 render48.62 03/25,17:53:54 00:00:15
At least the status is not sticking on "Run" but I don't understand
why the frames are differing so much - I will let it run on a few
more scenes before I hit the panic button!
Just though I'd leave an update!
It does seem odd that 4 renders kick in on the box, and two
take 30 mins to complete, and the other two take 20 seconds.
I guess jump over to the machine while the frames are taking
a while, and use 'strace' to see what shake is doing while
the frames are 'stuck' running, eg:
rsh render43
ps fax << determine the PID of the stuck shake process
strace -p <shake_PID> << see what shake is doing..
Also look in the logs while the frames are stuck to see
if there's any way to tell what shake is doing that it's
getting stuck on. (Turn on verbose mode if not already..)
--
Seriss Corporation
Tel: 626-795-5922
Fax: 626-795-5947
Cel: 310-266-8906