From: Brent Hensarling <brenth@(email surpressed)>
Subject: Re: Die frames
   Date: Tue, 08 Nov 2005 13:50:20 -0800
Msg# 1107
View Complete Thread (5 articles) | All Threads
Last Next
Its funny, I never noticed that there :)  What about the case where a frame is hung on a machine that is not dead, but the frame will not reque at all? We tend to get this all the time, and basically what I do is a restart on the rush service for the machine that has the hung frame, and it then reques the frame and then I can turn it back online and it will start rendering again. Will the down command just reque the frame and if the machine is still online, let it continue rendering?

_________________________________________________

Brent Hensarling

Luma Pictures

luma-pictures.com

_________________________________________________


On Nov 8, 2005, at 1:13 PM, Greg Ercolano wrote:

[posted to rush.general]

Patrick Boucher wrote:
One of our sysadmins here ripped 4 computers from the farm without first doing a 'rush -getoff [computernames...]'
When the job that was rendering on these nodes was dumped the frames wound up in Die state and are stuck and the job doesn't want to dump.
Is there any way to tell rush that it won't be getting a return code from the nodes and just forget about it?

Yes; the 'Down' button in irush is precisely for this purpose.

1) Click 'Frames'
2) Highlight the 'Die' frames waiting for the remotes to come back
3) Click the red 'Down' button

For more info on the irush 'Down' button, right click on it to view the help.

The equivalent command line option is 'rush -down'; for more info on that, see:

-- 
Rush Render Queue, http://seriss.com/rush/
Tel: xxx-xxx-xxxx
Cel: 310-266-8906
Fax: xxx-xxx-xxx


Last Next