Linux application crashing
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 ***
maya encountered a fatal error
Signal: 11 (Unknown Signal)
MDataBlock::inputArrayValue(MObject const&, MStatus*)
shaveHairShape::compute(MPlug const&, MDataBlock&)
THsurfaceShape::computePlug(Tplug const&, TdataBlock&)
Tplug::getValue(TdataHandle&, TdataBlock const&, bool, bool, bool) const
TdependNode::getPlugValue(Tplug const&, TdataHandle&, TdgContext const&)
MPlug::getValue(float&, MDGContext&) const
initTexInfoLookup(MObjectArray const&, MString, bool, bool)
shaveRenderer::doShutter(MTime const&, shaveConstant::ShutterState)
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.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide