On 04/12/12 09:39, wattana wrote:
> ###
> ### p00.466: 1086
> ###
> --------------- Rush 102.42a8 --------------
> -- Host: p02
> -- Pid: 18270
> -- Title: seq09pln12_person
> -- Jobid: p00.464
> -- Frame: 1086
> [..]
>
>
> But next lines show that the jobID has changed to 464, and all the rest
> info is from another job, frame and file...
This means the two jobs are rendering over each other's logs.
Sounds like jobid p00.466 and p00.464 both were
rendering the same scene and frame range.
The default behavior of rush is to use the scene file
as the directory for the log, if you render the same
scene file with the same frame range, the logs will
overwrite each other.
464 is likely the older job, but because it's log is being
shown, one of these scenarios is probably the issue:
> Someone requeued frame 1086 in the older job /after/
the newer job finished rendering that frame, causing
the older job's log to overwrite the newer one
> Both renders were running at the same time, and the
older job just happened to take longer to get to rendering
that frame
> The newer job hasn't actually rendered that frame yet
(ie. new job's frame 1086 is still in the Que state)
and so trying to view the log for it shows the older job's log
..and I'd probably rule out:
> A caching issue is showing the older log instead of the newer one
(ie. client side caching of the file system, oplocks, etc)
..just because you say you see the same results on different machines.
--
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)
|