I got those permissions problems you described, and with the help of a certain perl expert I know (cough cough...greg...cough), I put the following into my
submit.afterfx.pl to parse for that error. It's since become a distant memory. I actually had this in previous versions of AE as well.
I could sit with you and discuss *many* things about aerender that bother me, it seems to get worse with each version.
# INVOKE AERENDER, CHECK FOR ERRORS
print "\nExecuting: $command\n";
$exitcode = RunCommand($command, \$errmsg);
if ( $exitcode == 9 )
{
# VICTOR WANTS CHECK FOR "FALSE ERRORS" FROM AE
# "there is an annoying failure that AE exits on, and it actually does
# fail the frame. It's a false error, just ae being stupid. It says
# "Can not create a file in directory /blah/blah. Try checking write permissions."
# and returns an exit code of 9. I don't want to auto-requeue on every exit code 9,
# just the one that says "Try checking write permissions."
my $logmsg = LogCheck("^Executing: ",
(
"Try checking write permissions."
) );
if ( $logmsg ne "" )
{
print STDERR "--- AE EXIT 9: FALSE ERROR DETECTED: $logmsg\n";
system("rush -fu -notes $ENV{RUSH_FRAME}:\"RETRY: AE EXIT 9 FALSE ERROR\"");
exit(2); # RETRY
}
}
Best,
Vic
On Mar 8, 2011, at 8:36 AM, Gary Jaeger wrote:
On Mar 7, 2011, at 10:16 AM, Greg Ercolano wrote:
1) What OS on the file server (Mac OSX 10.??, Linux, Netapp, etc)
OSX 10.6 Server
2) What OS on the render nodes?
10.6
3) What file network system (NFS, SMB/CIFS, AFP, etc)
AFP
I'll get you the log asap.
. . . . . . . . . . . .
Gary Jaeger // Core Studio
86 Graham Street, Suite 120
San Francisco, CA 94129
415 543 8140