Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B54EC1777B for ; Thu, 16 Apr 2015 22:49:56 +0000 (UTC) Received: (qmail 81536 invoked by uid 500); 16 Apr 2015 22:49:50 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 81423 invoked by uid 500); 16 Apr 2015 22:49:50 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 81411 invoked by uid 99); 16 Apr 2015 22:49:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Apr 2015 22:49:49 +0000 X-ASF-Spam-Status: No, hits=3.5 required=5.0 tests=FSL_HELO_BARE_IP_2,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of cnauroth@hortonworks.com designates 64.78.52.187 as permitted sender) Received: from [64.78.52.187] (HELO relayvx12c.securemail.intermedia.net) (64.78.52.187) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Apr 2015 22:49:45 +0000 Received: from securemail.intermedia.net (localhost [127.0.0.1]) by emg-ca-1-2.localdomain (Postfix) with ESMTP id 3A3D153E8A for ; Thu, 16 Apr 2015 15:49:24 -0700 (PDT) Subject: Re: Container exited with a non-zero exit code 134 MIME-Version: 1.0 x-echoworx-emg-received: Thu, 16 Apr 2015 15:49:24.224 -0700 x-echoworx-msg-id: ce1773d8-1d8d-43d2-9331-5a6af6fe5765 x-echoworx-action: delivered Received: from 10.254.155.17 ([10.254.155.17]) by emg-ca-1-2 (JAMES SMTP Server 2.3.2) with SMTP ID 205 for ; Thu, 16 Apr 2015 15:49:24 -0700 (PDT) Received: from MBX080-W4-CO-1.exch080.serverpod.net (unknown [10.224.117.101]) by emg-ca-1-2.localdomain (Postfix) with ESMTP id 03B1D53E8A for ; Thu, 16 Apr 2015 15:49:24 -0700 (PDT) Received: from MBX080-W4-CO-2.exch080.serverpod.net (10.224.117.102) by MBX080-W4-CO-1.exch080.serverpod.net (10.224.117.101) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Thu, 16 Apr 2015 15:49:22 -0700 Received: from MBX080-W4-CO-2.exch080.serverpod.net ([10.224.117.102]) by mbx080-w4-co-2.exch080.serverpod.net ([10.224.117.102]) with mapi id 15.00.1044.021; Thu, 16 Apr 2015 15:49:22 -0700 From: Chris Nauroth To: "user@hadoop.apache.org" Thread-Topic: Container exited with a non-zero exit code 134 Thread-Index: AQHQeJJs7rmk+S6J6UmUneychyqSAp1QPgCA Date: Thu, 16 Apr 2015 22:49:21 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [50.248.208.113] x-source-routing-agent: Processed Content-Type: multipart/alternative; boundary="_000_D15587E91F995cnaurothhortonworkscom_" X-Virus-Checked: Checked by ClamAV on apache.org --_000_D15587E91F995cnaurothhortonworkscom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello Nitin, When I see an exit code greater than 128, then that makes me think the proc= ess didn't exit normally and instead it was terminated unexpectedly by a si= gnal. 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 =3D 6, which i= s SIGABRT. That would indicate something very unexpected happened inside t= he 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 co= uld look for hs_err_pid files that show the state of the JVM before the cra= sh. If the container was running native code, then you might see a core du= mp. Hope this helps. Chris Nauroth Hortonworks http://hortonworks.com/ From: Nitin Mathur > Reply-To: "user@hadoop.apache.org" > Date: Thursday, April 16, 2015 at 3:11 PM To: "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 stra= ight forward here. - Nitin --_000_D15587E91F995cnaurothhortonworkscom_ Content-Type: text/html; charset="us-ascii" Content-ID: <09E7728168A2E6489B1A77F0E09B1A2B@exch080.serverpod.net> Content-Transfer-Encoding: quoted-printable
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 =3D 6, which is SIGABRT.  Th= at 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 terminati= on.  If this was a MapReduce job or some other kind of Java process, t= hen you could look for hs_err_pid files that show the state of the JVM befo= re the crash.  If the container was running native code, then you might see a core dump.

Hope this helps.

Chris Nauroth
Hortonworks


From: Nitin Mathur <ntnmathur@gmail.com>
Reply-To: "user@hadoop.apache.org" <user@hadoop.apache.org>
Date: Thursday, April 16, 2015 at 3= :11 PM
To: "user@hadoop.apache.org" <user@hadoop.apache.org>
Subject: Container exited with a no= n-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


 --_000_D15587E91F995cnaurothhortonworkscom_--