Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 71751 invoked from network); 5 Nov 2010 12:13:39 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Nov 2010 12:13:39 -0000 Received: (qmail 3792 invoked by uid 500); 5 Nov 2010 12:14:08 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 3739 invoked by uid 500); 5 Nov 2010 12:14:06 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 3627 invoked by uid 99); 5 Nov 2010 12:14:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Nov 2010 12:14:05 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of michael_segel@hotmail.com designates 65.55.34.218 as permitted sender) Received: from [65.55.34.218] (HELO col0-omc4-s16.col0.hotmail.com) (65.55.34.218) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Nov 2010 12:13:59 +0000 Received: from COL117-W12 ([65.55.34.201]) by col0-omc4-s16.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 5 Nov 2010 05:13:38 -0700 Message-ID: Content-Type: multipart/alternative; boundary="_dfe1d302-a1fc-45b4-a335-e07d3c95c938_" X-Originating-IP: [173.15.87.33] From: Michael Segel To: Subject: RE: namenode and jobtracker remote access problem Date: Fri, 5 Nov 2010 07:13:38 -0500 Importance: Normal In-Reply-To: <1288958659.5264.12.camel@expat> References: <1288956210.12281.24.camel@linux-elo4.site>,,<1288958659.5264.12.camel@expat> MIME-Version: 1.0 X-OriginalArrivalTime: 05 Nov 2010 12:13:38.0781 (UTC) FILETIME=[E0E5F0D0:01CB7CE2] --_dfe1d302-a1fc-45b4-a335-e07d3c95c938_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Well... 0.0.0.0 means that its listening on all networks and in your case... eth0 a= nd 127.0.0.1. I'd try adding your client to the /etc/hosts on the machines. > Subject: RE: namenode and jobtracker remote access problem > From: henning.blohm@zfabrik.de > To: common-user@hadoop.apache.org > Date: Fri=2C 5 Nov 2010 13:04:19 +0100 >=20 > Hi Mike=2C >=20 > 1) yes. My client can ssh into any of nodes. > 2) No=2C unfortunately not (hosted machines=2C no domain yet=2C just IP > addresses). My client is not in /etc/hosts of any of the nodes. Why? > Would they do reverse lookups? > 3) looking at ifconfig's output there is only eth0 and lo. So I assume > that is a yes to your question. >=20 > My wild guess is that the namenode (and jobtracker) code by default try > to resolve the host name specified in fs.default.name and > mapred.job.tracker resp.=20 > and use the resulting IP to open the server socket (or channel). Rather > than 0.0.0.0.=20 >=20 > But if that was the case=2C many=2C really many people should have the sa= me > problem.... >=20 > Thanks=2C > Henning >=20 >=20 > Am Freitag=2C den 05.11.2010=2C 06:55 -0500 schrieb Michael Segel: >=20 > > Hi=2C > >=20 > > First things to check... > >=20 > > 1) Can you ping the machines from an external client machine. > > 2) /etc/hosts? Not a centralized DNS server? Is your client also in you= r /etc/hosts? > > 3) Do you only have one active NIC card? > >=20 > > And of course I'm assuming that when you say you have the cloud up=2C y= ou can launch jobs on the namenode and they run on all of the nodes? > >=20 > > -Mike > >=20 > > > Subject: namenode and jobtracker remote access problem > > > From: henning.blohm@zfabrik.de > > > To: common-user@hadoop.apache.org > > > Date: Fri=2C 5 Nov 2010 12:23:30 +0100 > > >=20 > > > Hi=2C > > >=20 > > > I have problems making namenode and jobtracker remotely accessible. > > >=20 > > > It seems several people have had this problem before but I was=20 > > > unfortunately not able to find a solution yet. > > >=20 > > > I have a hadoop 0.20.6 cluster setup. All nodes with static IP > > > addresses=2C=20 > > > all wired up via short names=2C data0=2C data1=2C data2=2C master in = /etc/hosts. > > >=20 > > > The master node hosts the name node as well as the job tracker. Both > > > listen > > > only to connection from the master node and will not accept remote=20 > > > connections: > > >=20 > > > > netstat -nltp > > >=20 > > > Proto Recv-Q Send-Q Local Address Foreign Address > > > State PID/Program name > > > tcp 0 0 127.0.0.1:3306 0.0.0.0:* > > > LISTEN - =20 > > > tcp 0 0 0.0.0.0:10000 0.0.0.0:* > > > LISTEN - =20 > > > tcp 0 0 0.0.0.0:22 0.0.0.0:* > > > LISTEN - =20 > > > tcp6 0 0 a.b.c.d:60000 :::* LISTE= N > > > 19800/java =20 > > > tcp6 0 0 :::52038 :::* > > > LISTEN 19235/java =20 > > > tcp6 0 0 a.b.c.d:9000 :::* LISTE= N > > > 19235/java =20 > > > tcp6 0 0 a.b.c.d:9001 :::* LISTE= N > > > 19507/java =20 > > > tcp6 0 0 :::60010 :::* > > > LISTEN 19800/java =20 > > > tcp6 0 0 :::50090 :::* > > > LISTEN 19409/java =20 > > > tcp6 0 0 :::56429 :::* > > > LISTEN 19507/java =20 > > > tcp6 0 0 :::2222 :::* > > > LISTEN 19717/java =20 > > > tcp6 0 0 :::50030 :::* > > > LISTEN 19507/java =20 > > > tcp6 0 0 :::38126 :::* > > > LISTEN 19409/java =20 > > > tcp6 0 0 :::80 :::* > > > LISTEN - =20 > > > tcp6 0 0 :::21 :::* > > > LISTEN - =20 > > > tcp6 0 0 :::50070 :::* > > > LISTEN 19235/java =20 > > > tcp6 0 0 :::22 :::* > > > LISTEN - =20 > > >=20 > > > (changed the real IP address to a.b.c.d).=20 > > >=20 > > > My hadoop/conf/core-site.xml looks like this: > > >=20 > > > > > > > > > > > > > > > > > > fs.default.name > > > hdfs://master:9000 > > > > > > > > > hadoop.tmp.dir > > > /home/hadoop/data > > > > > > > > >=20 > > > and hadoop/conf/mapred-site.xml like this: > > >=20 > > > > > > > > > > > > > > > > > > mapred.job.tracker > > > master:9001 > > > > > > > > >=20 > > >=20 > > > Using IP adresses rather than host names in core-site.xml or > > > hdfs-site.xml didn't > > > change anything (contrary to what other mailing list submissions > > > suggest). > > >=20 > > > Otherwise=2C the cluster starts up fine=2C all processes running=2C w= eb > > > interfaces are reachable=20 > > > and report nothing unusual. > > >=20 > > > Any idea? I am blocked :-( > > >=20 > > > Thanks=2C > > > Henning > > >=20 > > =20 = --_dfe1d302-a1fc-45b4-a335-e07d3c95c938_--