Hi Friends,

We are running Autodesk Maya 8.5 (64 bit) on opensuse 10 and 10.1 (both 64 bit OS) on 400 servers. These servers comprise of HP proliant blade server and IBM x336 series 1U servers.

These servers are configured as render farms for distributed processing (rendering) of maya scenes. The job distribution and scheduling is carried out by a third party software. Maya scenes are comprised of multiple frames. Each frame is rendered on individual server.

Of late we are facing an issue of maya crashing with multiple errors. But the errors are intermittent and the same frame gets rendered on the same server after resubmission.

Error 1 :


*** glibc detected *** /usr/autodesk/maya8.5-x64/bin/maya.bin: free(): invalid pointer: 0x00002aab18cf9010 ***
257.log:*** glibc detected *** /usr/autodesk/maya8.5-x64/bin/maya.bin: free(): invalid pointer: 0x000000001624faa0 ***
257.log:*** glibc detected *** /usr/autodesk/maya8.5-x64/bin/maya.bin: free(): invalid pointer: 0x00002aab1999f010 ***

Error 2:


maya encountered a fatal error

Signal: 11 (Unknown Signal)
Stack trace:
/lib64/libpthread.so.0 [0x2aef7abd0140]
TdataNurbsCurve::madeIntoNonWriter()
TdataLetter::unreference(TdataRefType)
Tdata::makeHolder()
TdataBlockDG::value(Tattribute const&)
MDataBlock::inputArrayValue(MObject const&, MStatus*)
shaveHairShape::computeOutputMesh(MDataBlock&, bool)
shaveHairShape::compute(MPlug const&, MDataBlock&)
THsurfaceShape::computePlug(Tplug const&, TdataBlock&)
TdependNode::dbEvaluate(TmsgEval&)
TdagObject::dbEvaluate(TmsgEval&)
Tplug::getValue(TdataHandle&, TdataBlock const&, bool, bool, bool) const
TdependNode::getPlugValue(Tplug const&, TdataHandle&, TdgContext const&)
TdependNode::processMessage(Tmsg&)
TdagObject::processMessage(Tmsg&)
Tmsg::send()
TmsgPlugValue::send()
MPlug::getValue(float&, MDGContext&) const
shaveHairShape::getHairNode()
initTexInfoLookup(MObjectArray const&, MString, bool, bool)
shaveRenderer::doShutter(MTime const&, shaveConstant::ShutterState)
shaveMRRenderer::frameStart(shaveGlobals::Globals const&)
shaveRender::frameStart(void*)
shaveRenderCmd::doIt(MArgList const&)
THcommandObject::doIt(TargList&)
TmetaCommand::doCommand(TargList&)
Mel_Command_Dispatch(SphNode*)
node_exec
fc_if
node_exec

Result: /casl-st5/Render/AO_SEQ_CHAR/SQ05_CHAR_FINAL/scenes/AO_SQ005_SC012_101_257_WINSTON_FUR_RIM_V03.ma
Fatal Error. Attempting to save in /usr/tmp/render.20090430.0112.ma
Writing crash report in /usr/tmp/render.20090430.0112.crash
// Maya exited with status 1

What could these error mean and how can I troubleshoot them ? I have added following environment variables in /etc/profile for more details on the error.

export MAYA_DEBUG_ENABLE_CRASH_REPORTING=1
export MALLOC_CHECK_=1

__________________________

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Use this guide to trouble shoot the crash : http://www.bitwizard.nl/sig11/

It looks like it may be a full scratch disk "Fatal Error. Attempting to save in /usr/tmp/render.20090430.0112.ma". This is assuming the directory exists and the permissions are correct. I came to the guess from your statement "the errors are intermittent". The disk may have more space or less space at different times.

__________________________

Jay

Post new comment

Please note that comments may not appear immediately, so there is no need to repost your comment.
The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <pre> <ul> <ol> <li> <dl> <dt> <dd> <i> <b>
  • Lines and paragraphs break automatically.

More information about formatting options

Newsletter

Each week Linux Journal editors will tell you what's hot in the world of Linux. You will receive late breaking news, technical tips and tricks, and links to in-depth stories featured on www.linuxjournal.com.
Sign up for our Email Newsletter

Tech Tip Videos

From the Magazine

December 2009, #188

If last month's Infrastrucuture issue was too "big" for you then try on this month's Embedded issue. Find out how to use Player for programming mobile robots, build a humidity controller for your root cellar, find out how to reduce the boot time of your embedded system, and if you're new to embedded systems find out the basics that go into one. You can also read about the Beagle Board, the Mesh Potato and a spate of other interestingly named items. And along with our regular columns don't miss our new monthly column: Economy Size Geek.


Read this issue