Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of jason.hadoop@gmail.com
 designates 209.85.212.188 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=RShkFZvVDjLy2Nr1OJI0bQE/ETsPCtbt1sE99OG1GEYFmsd3Jenj0j2LkkVUzmCI/K
         c/bROPjM5q5q6AMIe8hDCfSU+b4M++BNascekeHg9XzLNgUUNZFr6jr8gclo6yr+2/Af
         7ke6t3wqLrJM1x0C2vcrLyXtoSthCy4QtJzuE=
MIME-Version: 1.0
In-Reply-To: <873f8eb60907161354k424069d6p2ed135cb3cdae77e@mail.gmail.com>
References: <873f8eb60907151257r21498614q8775ec892afa2597@mail.gmail.com>
	 <873f8eb60907151309h767e5f68r83a0b80d30215ca@mail.gmail.com>
	 <b4da41030907151317s574a2332tc2f49c837a5545c1@mail.gmail.com>
	 <873f8eb60907151324k4400d567rd64c3b01c40d9e64@mail.gmail.com>
	 <b4da41030907151341m73523d8fu3350590370412bd8@mail.gmail.com>
	 <873f8eb60907151614x280e5b2dq65727835bbd5494@mail.gmail.com>
	 <001801ca0687$61f861e0$25e925a0$@com>
	 <873f8eb60907160753s5c489f59x3aa1a7e01f7bb81a@mail.gmail.com>
	 <8211a1320907160815m12bb9e75o13855fa046e931c4@mail.gmail.com>
	 <873f8eb60907161354k424069d6p2ed135cb3cdae77e@mail.gmail.com>
Date: Thu, 16 Jul 2009 22:55:12 -0700
Message-ID: <314098690907162255m409257dfo455092402ba7ac3c@mail.gmail.com>
Subject: Re: Datanode Cannot Connect To The Server
From: jason hadoop <jason.hadoop@gmail.com>
To: common-user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=001485e8d2168365bf046ee06e1e

--001485e8d2168365bf046ee06e1e
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

If your namenode is not binding to the ethernet port address, but only to
the localhost, your datanode will never be able to connect to it.

I vaguely remember that if the hostname of the node is found on the
localhost line in /etc/hosts, that this may happen.

On Thu, Jul 16, 2009 at 1:54 PM, Boyu Zhang <boyuzhang35@gmail.com> wrote:

> Thank you for your suggestion.
>
> I have done that plenty of times, and every time I delete the pids and the
> files /tmp/hadoop-name that namenode formate genrated. But I got the same
> error over and over.
>
>
> I found out that after I start-dfs.sh, I check the netstat -pnl(from the
> master),  there is a process listening on port 9000 with local address
> 127.0.0.2. But in the log file of the failed data node , it kept trying to
> connect to IP:9000 where IP is the actual IP of the master machine. And I
> tried to use IP address in stead of machine name, still not work. I am
> still
> trying to figure out why. It seems that not lots of people are having this
> problem, but I keep getting this error.
>
>
> Thanks a lot!
>
>
> On Thu, Jul 16, 2009 at 11:15 AM, zhang jianfeng <zjffdu@gmail.com> wrote:
>
> > It seems that your datanode is dead. My suggestion is that you can
> reformat
> > the namenode, and restart the cluster.
> >
>


-- 
Pro Hadoop, a book to guide you from beginner to hadoop mastery,
http://www.amazon.com/dp/1430219424?tag=jewlerymall
www.prohadoopbook.com a community for Hadoop Professionals

--001485e8d2168365bf046ee06e1e--