From: wattana <watttana@(email surpressed)>
Subject: wrong frame info
   Date: Thu, 12 Apr 2012 12:39:26 -0400

Hi!
First of all, sorry about my poor English, hope make myself clear (I'm 
from Spain).

I've been used Rush for four years. It always worked fine but in the last 
two months I am getting some weird messages when gathering frame info...

This is the output of one frame rendered:

###
### p00.466: 1086
###
--------------- Rush 102.42a8 --------------
--      Host: p02
--       Pid: 18270
--     Title: seq09pln12_person
--     Jobid: p00.464
--     Frame: 1086
--     Tries: 3
--     Owner: josea (701/508)
-- RunningAs: josea (701/508)
--  Priority: 101
--      Nice: 10
--    Tmpdir: /var/tmp/.RUSH_TMP.886
--   LogFile: /ddf/proyectos/Corazon_del_Roble/produccion/lighting/
secuencia09/pln12/seq09pln12_ilu.mb.log/1086
--   Command: perl /mnt/drqueue/rushscripts/submit-maya.pl -render 1 0 0 
0 yes 1 Fail /ddf/proyectos/Corazon_del_Roble/produccion/lighting/
secuencia09/pln12/seq09pln12_ilu.mb /../ddf/proyectos/Corazon_del_Roble/
produccion/lighting - mentalray(mr) all ray 5 0 off -rlperson - - off
--   Started: Thu Apr 12 16:34:00 2012


As you can see, the info starts with the correct info, p00.466: 1086

Machine: p00
JobID : 466
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...

I've checked from several machines, tried different path and job 
combinations with no luck. By the way nothing has changed in our render 
farm...

Thanks a lot for any help!

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)