Hi!
I found a strange behaviour of rush when a machine 'dies'. We have
several workstations here which are dualboot machines: Linux for Shake
and Windows for 3D and other stuff. Rush is only installed on Linux.
If one of these machines is active and rendering Shake on Linux, it
doesn't behave correctly when someone reboots this machine to windows
without setting it offline first in rush.
After the reboot I see this machine in rushtop with the chevron, but it
is still marked as active. Irush shows that this machine still renders
when I look at the "all jobs" listing. When I look at the 'frames'
listing of this job I see the package which was rendered on this machine
before reboot in an orange color and the comment says "retry#2 of 3
(New state will be 'Que')" and a "Die" status at the beginning of the line.
Problem is: it just doesnt't change to the "queue" status. And I can't
dump the whole jump or change the status of this packet. I think the
only chance to get back to normal behaviour is to reboot this machine to
linux so rush starts and helps to sort this out. But I can't reboot at
the moment.
Seems not be a good behaviour if rush can't deal with 'dying' machines.
Am I doing something completely wrong or is there a bug in rush?
Thanks for your help,
Abraham
--
Abraham Schneider
VFX Compositor
ARRI Film & TV Services GmbH
Tuerkenstr. 89
D-80799 Muenchen
Phone: +49 89 3809-1269
Mobile: +49 173 5719842
Email: aschneider@(email surpressed)
|