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 E2DADDAFC for ; Thu, 23 May 2013 23:20:23 +0000 (UTC) Received: (qmail 71899 invoked by uid 500); 23 May 2013 23:20:21 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 71855 invoked by uid 500); 23 May 2013 23:20:21 -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 71846 invoked by uid 99); 23 May 2013 23:20:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 May 2013 23:20:21 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jdcryans@gmail.com designates 209.85.212.54 as permitted sender) Received: from [209.85.212.54] (HELO mail-vb0-f54.google.com) (209.85.212.54) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 May 2013 23:20:15 +0000 Received: by mail-vb0-f54.google.com with SMTP id f13so2633773vbg.41 for ; Thu, 23 May 2013 16:19:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=hnDjH4jXbhCi860xhlv51UKbm59V71QNzreoxkjM99Q=; b=R2o2vd8QAMmiyidyznQ/kM4vz0pCZxu8PrZIUxF/7K0nOb3jGDSWHAtFUpZxyPlxTa Df+Btzi5ZCD1Z/STrPnmvisrndNIfCU9nnZ1R/0f0fN+dckcVG+a6yfSwwN3BZCiqhc2 7fZ5sBf7eOqlvtLEPL1Eax2B3gW+QCtsNk5/C6naurj3q4PFqQjhVGChGShInjYIp71g mUsYECinFTPQMfgjXJ6PJXSdXdnAtn99RxbeF3dUlvux/QoioT3/2D0OCdxH4Isbyzxz jmb+yMkZhjbpi89lmhe5VITggC5QJiSeEZxFonD1XRnF7p6sv9qppr8XkrzYTco1n1rN vDtw== MIME-Version: 1.0 X-Received: by 10.58.90.5 with SMTP id bs5mr6758084veb.60.1369351194826; Thu, 23 May 2013 16:19:54 -0700 (PDT) Sender: jdcryans@gmail.com Received: by 10.220.113.206 with HTTP; Thu, 23 May 2013 16:19:54 -0700 (PDT) In-Reply-To: References: <50124382-5140-4E08-B695-0417CAEF94FB@gmail.com> Date: Thu, 23 May 2013 16:19:54 -0700 X-Google-Sender-Auth: _fnBCsKiVPJ_tMbFQby4G3AWd24 Message-ID: Subject: Re: HBase is not running. From: Jean-Daniel Cryans To: "user@hbase.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org It should only be a matter of network configuration and not a matter of whether you are a Hadoop expert or not. HBase is just trying to get the machine's hostname and bind to it and in your case it's given something it cannot use. It's unfortunate. IIUC your machine is hosted on cox.net? And it seems that while providing that machine they at some point set it up so that its hostname would resolve to a public address. Sounds like a misconfiguration. Anyways, you can edit your /etc/hosts so that your hostname points to 127.0.0.1 or, since you are using 0.94.7, set both hbase.master.ipc.address and hbase.regionserver.ipc.address to 0.0.0.0 in your hbase-site.xml so that it binds on the wildcard address instead. J-D On Thu, May 23, 2013 at 4:07 PM, Yves S. Garret wrote: > How weird. Admittedly I'm not terribly knowledgeable about Hadoop > and all of its sub-projects, but I don't recall ever setting any networking > info to something other than localhost. What would cause this? > > > On Thu, May 23, 2013 at 6:26 PM, Jean-Daniel Cryans wrote: > >> That's your problem: >> >> Caused by: java.net.BindException: Problem binding to >> ip72-215-225-9.at.at.cox.net/72.215.225.9:0 : Cannot assign requested >> address >> >> Either it's a public address and you can't bind to it or someone else >> is using it. >> >> J-D >> >> On Thu, May 23, 2013 at 3:24 PM, Yves S. Garret >> wrote: >> > Here is my dump of the sole log file in the logs directory: >> > http://bin.cakephp.org/view/2116332048 >> > >> > >> > On Thu, May 23, 2013 at 6:20 PM, Jean-Daniel Cryans > >wrote: >> > >> >> On Thu, May 23, 2013 at 2:50 PM, Jay Vyas wrote: >> >> > 1) Should hbase-master be changed to localhost? >> >> > >> >> > Maybe Try changing /etc/hosts to match the actual non loopback ip of >> >> your machine... (i.e. just run Ifconfig | grep 1 and see what ip comes >> out >> >> :)) >> >> > and make sure your /etc/hosts matches the file in my blog post, (you >> >> need hbase-master to be defined in your /etc/hosts...). >> >> >> >> hbase.master was dropped around 2009 now that we have zookeeper. So >> >> you can set it to whatever you want, it won't change anything :) >> >> >> >> > >> >> > 2) zookeeper parent seems bad.. >> >> > >> >> > Change hbase-rootdir to "hbase" (in hbase.rootdir) so that it's >> >> consistent with what you defined in zookeeper parent node. >> >> >> >> Those two are really unrelated, /hbase is the default so no need to >> >> override it, and I'm guessing that hbase.rootdir is somewhere writable >> >> so that's all good. >> >> >> >> Now, regarding the "Check the value configured in >> >> 'zookeeper.znode.parent", it's triggered when the client wants to read >> >> the /hbase znode in ZooKeeper but it's unable to. If it doesn't exist, >> >> it might be because your HBase is homed elsewhere. It could also be >> >> that HBase isn't running at all so the Master never got to create it. >> >> >> >> BTW you can start the shell with -d and it's gonna give more info and >> >> dump all the stack traces. >> >> >> >> Going by this thread I would guess that HBase isn't running so the >> >> shell won't help. Another way to check is pointing your browser to >> >> localhost:60010 and see if the master is responding. If not, time to >> >> open up the log and see what's up. >> >> >> >> J-D >> >> >>