From: Greg Ercolano <erco@(email surpressed)>
Subject: Re: < MinTime then ReQueue
   Date: Wed, 16 Feb 2011 12:19:05 -0500
Msg# 2020
View Complete Thread (6 articles) | All Threads
Last Next
Craig Allison wrote:
> For the last couple of years I've been using Rush to create standardised =
> production QuickTimes from rendered frames, email the relevant groups, =
> publish frames, move data around the network etc and it's been working =
> really well overall, but I'm getting a reoccurring problem with the =
> initial render where it's immediately moving to state "Done" without the =
> render ever happening, when I click "Que" the job will then render =
> properly without complaint.

	Hmm, can you include some more info.. when this happens, paste me:

		1) The 'Frames' report for the first time it says 'Done' (but no render).
		   I'd like to see what machine it picked up on where it quickly became "done".

		1a) Is a frame log generated for that frame? If so, paste that here too.

		2) The 'Jobs Full' report for this job.

		3) The script that submits the job, and the script (if separate) that renders it.

		   It's possible the script is submitting the job in such a way
		   that the frame is forced to start in the 'Done' state on submit.
		   (It is possible to do this)

		4) The rushd.log from the machine that took the render the first time
		   (where the render time is 00:00:00)

> As the time elapsed on these problem jobs shows as 00:00:00 I thought =
> there might be a way of saying if job < 00:00:01 then ReQueue?

	You could make a done command that checks this and requeues it,
	but before you try covering up the problem, let's first try to
	determine the cause.

-- 
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)ext.23
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)

Last Next