Marco Recuay wrote:
> [posted to rush.general]
>
> Has anyone else encountered strange write permissions errors when
> rendering After Effects in OS X?
>
> aerender Error: After Effects error: Error in output for render queue
> item 1, output module 1. Can not create a file in directory
> /private/var/automount/blah/blah. Try checking write permissions.
>
> This error occurs on 3-5% of frames, and re-queuing works fine. This
> has occured on all AE versions from 6.5 to 8.0. There are no write
> permissions problems upon inspection, so I dont know how to solve it.
>
> This is on OS X 10.4.10, with NFS file shares.
>
> Any ideas?
Does the problem always seem to happen on a particular machine?
Possibly one or two machines don't have the file server mounted
properly.
To troubleshoot, try to replicate the problem from the
command line:
I) Look at one of the frames that fails with the error,
and make note of:
1) the machine it failed on
2) the 'RunningAs:' line in the frame log
II) Login to that machine using either ssh or telnet, logging in
as the same user shown the render was running as (ie. the 'RunningAs:'
line from the frame log)
III) From the unix prompt, try to access the directory in question, eg:
ls -la /private/var/automount/blah/blah
echo hello > /private/var/automount/blah/blah.txt
If you're able to replicate the error, then trouble shoot it that way.
Could be the mount to your file server is not mounted on that machine.
* * *
I should point out the path /private/var/automount/blah/blah
looks wrong.. that should probably be more like /Volumes/blah/blah
Me, I don't trust the automounter, and prefer to making static
mounts by hacking mount commands into the boot scripts, such as
is described in steps #3 and #4 of this article:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+1295+1295+1297+1298
Usually it just comes down to a simple command like:
mount -t nfs server:/somedir /jobs/somedir
..where /jobs/somedir is an empty directory that you mount your
file server onto via NFS.
Regardless of if it's a mount problem, or user access problem,
you should be able to replicate the problem from the unix prompt,
assuming you ssh or telnet over to the machine in question and
login as the same user the render was trying to run as.
--
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|