From: Jeff Yana <240vac@(email surpressed)>
Subject: Re: [Q+A] Using After Effects on OSX
   Date: Mon, 05 Dec 2005 10:45:59 -0800
Msg# 1137
View Complete Thread (10 articles) | All Threads
Last Next
Yes, I have confirmed that this process DOES work. With no current login (via WindowManager), AFP automounts functioning correctly, aerender setuid'd to root, AE renders perform flawlessly.

I think the problem I was having earlier was the known one of the Rush startup item failing at startup (I had just restarted thos test machines) under OS X (10.4 in this case). The jobs just remainged in a Queued state because Rush had not started on thos systems yet...

Greg Ercolano wrote:
	by www.3dsite.com (8.12.8/8.12.8) with SMTP id jB3NZL11019080

	for <rush decimal general at seriss decimal com>; Sat, 3 Dec 2005 15:35:21 -0800
Received: (qmail 90572 invoked from network); 3 Dec 2005 23:35:56 -0000
Received: from unknown (HELO ?192.168.0.9?) (unknown)

  by unknown with SMTP; 3 Dec 2005 23:35:56 -0000
X-pair-Authenticated: 24.205.137.195
Organization: Seriss Inc.
User-Agent: Thunderbird 1.5 (X11/20051025)
MIME-Version: 1.0
To: rush decimal general at seriss decimal com
In-Reply-To: <1132-rush decimal general at seriss decimal com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Path: 3dsite.com
Xref: 3dsite.com rush.general:1133
NNTP-Posting-Host: localhost

Jeff Yana wrote:

there is no error message, the job just remains in a queued state


	This doesn't sound like a window manager problem, or aerender even.

	It sounds like it's not starting the render at all, probably for a
	lower level reason, possibly mounts, or possible user accounts.

	In Irush, look at the 'Frames' and 'Cpus' reports under the NOTES column:
	are there any indications of an error? (uid unknown, file not found,
	access denied, not enough ram..)

	If not, are there any errors in the rushd.log on one of the render
	nodes that give any indications?


(and presumable fails after 3 retires, though I have not let it go that long to find out)


	If the TRY count is staying zero, and the frames are all Que,
	then rush isn't even running the frames at all; see the Cpus NOTES field
	for the reason why.

	If, however, the TRY count is clocking up, and there is no error under
	the NOTES field of the Frames or Cpus report, then Pause the job,
	and double click on the frame to see what the log says.

	(When rush can't open the log file, it puts error messages into the NOTES
	field of the "Frames" and/or "Cpus" report)


Last Next