Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 34552109CA for ; Thu, 2 May 2013 12:39:01 +0000 (UTC) Received: (qmail 59200 invoked by uid 500); 2 May 2013 12:38:59 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 59034 invoked by uid 500); 2 May 2013 12:38:58 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 59001 invoked by uid 99); 2 May 2013 12:38:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 May 2013 12:38:57 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [209.85.212.41] (HELO mail-vb0-f41.google.com) (209.85.212.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 May 2013 12:38:52 +0000 Received: by mail-vb0-f41.google.com with SMTP id x19so399845vbf.28 for ; Thu, 02 May 2013 05:38:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=2fDSutE+bKT0wLuqwMbeeg6FXS6J+CymT1ENVbvkqXU=; b=ZWJY7QnoYzPqpJ3tFFbNv5AcFPGslWRP3vlxM0ZQ5jltdVJ0dJydengb41BkKqoI2f J874t0/v+l6yngU5Pgq+c4tETo92jNzE7ADnFB4nXiitIlu7Oml5KYpWZ+sswa0z6SwY 0xxxaSjOtA/jviARslAEuJadDD5dKG3xgyPm5G+qWul1GP4cVxtpUooMgEd6BpEj/k6X whxkul4AtIZBQLqJy18uhJBDyoPjeX8ufXmZrO0LGSy3BatV3NlyoKI8bAdGkCasd0C1 bB+KJ6sg7bSGUNnW4w/V5dlW1SexxDEsT+SVEJj9oZdgdu5BaDRzNkwEaAq//6sQHXMP IJ2w== X-Received: by 10.52.71.4 with SMTP id q4mr1791200vdu.8.1367498290935; Thu, 02 May 2013 05:38:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.227.130 with HTTP; Thu, 2 May 2013 05:37:50 -0700 (PDT) In-Reply-To: References: From: Jean-Marc Spaggiari Date: Thu, 2 May 2013 08:37:50 -0400 Message-ID: Subject: Re: JVM seg fault in HBase region server To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=bcaec50160f1dcd12c04dbbb819a X-Gm-Message-State: ALoCoQk7oGBsu9tX6jLzCq/ANWTgUIdjhsMdGLh1waSLZmXFTyw7Xuv7GlzizR3zPG3pK8BNhBrC X-Virus-Checked: Checked by ClamAV on apache.org --bcaec50160f1dcd12c04dbbb819a Content-Type: text/plain; charset=UTF-8 Hi Varun, Never faced this error ever. And I faced a lot ;) Even by running with OpenJDK 1.x. and I'm running eglibc on all my servers. ldd --version ldd (Debian EGLIBC 2.13-38) 2.13 Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by Roland McGrath and Ulrich Drepper. JM 2013/5/1 Varun Sharma > From what I see from > ldd --version > ldd (Ubuntu EGLIBC 2.15-0ubuntu10.3) 2.15 > > We are running eglibc which is somewhat different from glibc - > http://en.wikipedia.org/wiki/Embedded_GLIBC. > > It seems that this is a problem with Ubuntu, have folks seen this on non > ubuntu installs ? > > Thanks > Varun > > > On Wed, May 1, 2013 at 1:54 PM, Varun Sharma wrote: > > > Hi, > > > > I am seeing the following which is a JVM segfault: > > > > hbase-regionser[28734]: segfault at 8 ip 00007f269bcc307e sp > > 00007fff50f7e638 error 4 in libc-2.15.so[7f269bc51000+1b5000] > > > > Benoit Tsuna reported a similar issue a while back - > > > http://blog.tsunanet.net/2011/05/jvm-u24-segfault-in-clearerr-on-jaunty.html > > > > I wonder if there was ever a resolution on the issue. We are running java > > version "1.6.0_38" > > , ubuntu precise 12.04 - kernel 3.2. The libc version from the above line > > seems to be 2.15. > > > > I wonder if people have seen this in the past and if yes, were they able > > to resolve it and if yes, then how ? Was it a VM upgrade, a kernel > upgrade > > or a libc upgrade ? > > > > Thanks > > Varun > > > > > > > --bcaec50160f1dcd12c04dbbb819a--