Looks like the kernel change was a "happy coincidence", it certainly solved my multi cpu issue (only one was seen) and it seemed that it also solved my status "Run" issue, but it looks like this was more shake script specific than an actual solution.
I'd noticed that the /tmp partition was being filled to 100% as it was relatively small so I've reconfigured that today so that's there's plenty of headroom, this has fixed the "Run" status issue but now I'm getting wildly differing render times for consecutive frames. See below:
Done 0002 3 render43 4773 render48.62 03/25,16:58:19 00:23:43
Done 0003 3 render43 4775 render48.62 03/25,16:58:19 00:23:42
Done 0004 3 render43 4828 render48.62 03/25,17:22:02 00:00:18
Done 0005 3 render43 4836 render48.62 03/25,17:22:03 00:00:17
Done 0006 3 render43 4846 render48.62 03/25,17:22:21 00:00:22
Done 0007 3 render43 4848 render48.62 03/25,17:22:21 00:00:22
Done 0008 3 render43 4864 render48.62 03/25,17:22:44 00:00:34
Done 0009 3 render43 4866 render48.62 03/25,17:22:44 00:00:34
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!
Cheers
Craig
Craig Allison
Digital Systems & Data Manager
The Senate Visual Effects
Twickenham Film Studios
St.Margarets
Twickenham
TW1 2AW
t: 0208 607 8866
www.senatevfx.com
On 20 Mar 2008, at 19:12, Greg Ercolano wrote:
[posted to rush.general]
Craig Allison wrote:
Sorry about the delay getting back on this one, I've been very busy!
The problem was intermittent but a change of kernel seems to have
eradicated the problem altogether...
Thanks for the follow up, Craig..
So the problem was with the default Debian 4 + Shake 4.1 combo.
Interesting.
Just curious: is it a known issue where a kernel upgrade was
a known solution, or was it just a happy coincidence?
If it was a known issue, guess I'd be curious to see any links
that might have helped you, in case they cover details as to the
cause, in case it's something I should watch out for across the
board with linux.
--
Seriss Corporation
Tel: 626-795-5922
Fax: 626-795-5947
Cel: 310-266-8906