hadoop-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Nauroth <cnaur...@hortonworks.com>
Subject Re: Container exited with a non-zero exit code 134
Date Thu, 16 Apr 2015 22:49:21 GMT
Hello Nitin,

When I see an exit code greater than 128, then that makes me think the process didn't exit
normally and instead it was terminated unexpectedly by a signal.  On most of the systems I've
used, if a process gets killed, then the reported exit status is 128 + the signal number.
 134 - 128 = 6, which is SIGABRT.  That would indicate something very unexpected happened
inside the process (i.e. memory corruption) and it chose to call the abort function.

You might try looking for other evidence of abnormal program termination.  If this was a MapReduce
job or some other kind of Java process, then you could look for hs_err_pid files that show
the state of the JVM before the crash.  If the container was running native code, then you
might see a core dump.

Hope this helps.

Chris Nauroth

From: Nitin Mathur <ntnmathur@gmail.com<mailto:ntnmathur@gmail.com>>
Reply-To: "user@hadoop.apache.org<mailto:user@hadoop.apache.org>" <user@hadoop.apache.org<mailto:user@hadoop.apache.org>>
Date: Thursday, April 16, 2015 at 3:11 PM
To: "user@hadoop.apache.org<mailto:user@hadoop.apache.org>" <user@hadoop.apache.org<mailto:user@hadoop.apache.org>>
Subject: Container exited with a non-zero exit code 134

Hi All,

Production job failing with Container exited with a non-zero exit code 134. Any ideas what
could be causing this as I am not able to see anything straight forward here.

- Nitin

View raw message