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)
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)
|