PipelineFX Forum
Qube! => General => Topic started by: uppi on December 03, 2012, 11:51:34 AM
-
Hi,
any idea For below mentioned error to fix .
ERROR: maximum nudge count
timed out-- aborting! at C:\Program Files\pfx\jobtypes/maya/MelProcessor.pm line 569.
maya::MelProcessor::abort
ERROR: exception caught in maya::UniversalMayaRenderJob=HASH(0x4082ad8)->run()
aborting at C:\Program Files\pfx\jobtypes/maya/MelProcessor.pm line 137.
INFO: reporting status [failed] to supe: qb::reportjob('failed')
maya::MelProcessor::DESTROY
maya::MelProcessor::finish
INFO: HARNESS=[IPC::Run=HASH(0x41e2388)]
ERROR: did maya crash earlier? at C:\Program Files\pfx\jobtypes/maya/MelProcessor.pm line 106 during global destruction.
upender
-
When Qube's jobtype looses track of Maya, it "nudges" Maya to see if it's still awake. After X number of nudges, it determines Maya is dead & fails the frame. That conversation is what you've copy/pasted.
The moral: Maya crashed during rendering. Why it crashed cannot be seen in these logs & may not be visible in the logs.
- See if there are any errors earlier in the logs that might allude to a reason for crashing.
- Check the machine's vitals at the time of the crash - did it run out of memory/swap, hard drive space, kernel error, network problem?
- Try rendering the frame in question on the same machine again.
- Try rendering the frame in question on a different machine.
- As a last resort, try rendering the frame with Batchrender. If it fails, log into the render node (preferably as your proxy user), right-click the Batchrender job, then choose "execute in local shell" to see if you get a better indication of why it crashed.
These types of issues are almost always related to the scene file, itself.