From: Victor DiMichina <victor@(email surpressed)>
Subject: Re: aerender batch framing
   Date: Mon, 14 Mar 2011 18:38:06 -0400
Msg# 2054
View Complete Thread (4 articles) | All Threads
Last Next
On Mar 14, 2011, at 3:31 PM, Greg Ercolano wrote:

> [posted to rush.general]
> 
> Victor DiMichina wrote:
>> Anyone have the issue with batching aerender where ae returns an exitcode of 0 "success" yet only renders a portion of the batch?    I've attached two log files,  one is 
>> 
>> "aerender_full_success.rtf"  showing a log from a successful 10-frame batch,  highligting the batch frames,  and the output.   So the node was asked to render frames 211-220, and it rendered them all,  exiting with a success code.
>> 
>> "aerender_partial_false_success.rtf"  shows a log from an attempted 10-frame batch (same job),   and shows the output being only one frame.    Sometimes it's one,  sometimes it will do three,  five,  it's all random.   
>> 
>> 
>> AE has many weirdnesses that I have to deal with,   but usually I can parse for errors and auto-requeue the frame.   This one shows no difference that I can see in the log,  it just doesn't render the frames.
>> 
>> Anyone seen this?    I want to report this to Adobe.     I also want to find a pattern here to check for this and re-queue frames.
> 
> 	Is it the case where when you requeue the batch, it works fine the next time,
> 	even on the same machine?
> 
> 	You should report it, as AE is probably not reporting errors correctly here.
> 
> 	To see what's actually happening, check your client and file server's
> 	system logs (eg. /var/log/system.log, /var/log/secure.log, /var/log/samba*)
> 	to see if the network file system is generating spurious permission errors
> 	or some such.
> 
> 	I've seen a few cases where e.g. the /var/log/system.log of mac file servers
> 	reported random kerberos that resulted in 'permission denied' situations
> 	only with AE + NFS, and AE + samba. It seemed like a two part problem;
> 	1) AE was exacerbating an OS problem to occur (fault of the OS), and
> 	2) AE wasn't reporting the OS error in the logs (fault of AE).
> 
> 	You should report it to Adobe I think.

I will report it to Adobe.    Not sure how confident I am that they'll care,  but it's worth a try.
We're OS X server with AFP share.    it's been doing this before 10.6,  but I recently started batch framing,  so I don't know if previous versions of OS X server/client/AE had this problem.  

> 	I've seen other customers run into this, and it's mostly been recently
> 	(last few months). Not sure if it's something to do with a recent upgrade
> 	of OSX, or AE, or some magic combo.

It's been pre-10.6 for me,  At least since 10.3

Cheers,
Vic

> 
> 	BTW, is your file server MacOS? I've seen a pattern of this where the
> 	server was a recent release of OSX (Snow Leopard/10.6).
> 
> -- 
> Greg Ercolano, erco@(email surpressed)
> Seriss Corporation
> Rush Render Queue, http://seriss.com/rush/
> Tel: +1 626-576-0010 ext.23
> Fax: +1 626-576-0020
> Cel: +1 310-266-8906


Last Next