Return-Path: 
 <common-user-return-32026-apmail-hadoop-common-user-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-common-user-archive@www.apache.org
Delivered-To: apmail-hadoop-common-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 6ABD89285
	for <apmail-hadoop-common-user-archive@www.apache.org>;
 Mon,  9 Jan 2012 21:33:42 +0000 (UTC)
Received: (qmail 18643 invoked by uid 500); 9 Jan 2012 21:33:38 -0000
Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org
Received: (qmail 18586 invoked by uid 500); 9 Jan 2012 21:33:37 -0000
Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-user@hadoop.apache.org>
List-Id: <common-user.hadoop.apache.org>
Reply-To: common-user@hadoop.apache.org
Delivered-To: mailing list common-user@hadoop.apache.org
Received: (qmail 18578 invoked by uid 99); 9 Jan 2012 21:33:37 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jan 2012 21:33:37 +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 (athena.apache.org: domain of iefinkel@gmail.com designates
 209.85.210.176 as permitted sender)
Received: from [209.85.210.176] (HELO mail-iy0-f176.google.com)
 (209.85.210.176)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jan 2012 21:33:31 +0000
Received: by iapp10 with SMTP id p10so9514783iap.35
        for <common-user@hadoop.apache.org>;
 Mon, 09 Jan 2012 13:33:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        bh=hYhmvNi4TcWE0/vHCV3LjHrUUELnjAlnofIy6PNtdg4=;
        b=mh2dgtdQsU76QRj4XHN6N0VUOOFR9Bn4DuKOWY8iyWoSUlHMV7G2gT5ERJYFkWrZ/n
         pHLTDgBnDtaTPTvil8KhneA15FzPJ1qh1JcoQnxAMTyszwUwv0nqBJHQZW0sd9ccXBbk
         rHb7bO8dztuTErBFLoCeoDNrEYqJn8NUTAdBI=
Received: by 10.43.45.137 with SMTP id uk9mr19538904icb.52.1326144790530;
        Mon, 09 Jan 2012 13:33:10 -0800 (PST)
Received: from Eli-Finkelshteyns-MacBook-Pro.local ([38.112.1.90])
        by mx.google.com with ESMTPS id
 g34sm255289587ibk.10.2012.01.09.13.33.09
        (version=SSLv3 cipher=OTHER);
        Mon, 09 Jan 2012 13:33:10 -0800 (PST)
Message-ID: <4F0B5D18.9090000@gmail.com>
Date: Mon, 09 Jan 2012 16:33:12 -0500
From: Eli Finkelshteyn <iefinkel@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: common-user@hadoop.apache.org
Subject: Re: Netstat Shows Port 8020 Doesn't Seem to Listen
References: <4F0B2E6E.8080204@gmail.com> <4F0B38BF.10708@gmail.com>
 <CAF-umFO5Qp5iae5Hx_0ft73OW_x863thvQjsTgMOOmRYX_VCWQ@mail.gmail.com>
 <4F0B4214.2050600@gmail.com>
 <CAHAmRctFQ0HEAwrfv-gY5D=PxEqMwP+YvHmz_SaL84WR4ZA+=w@mail.gmail.com>
In-Reply-To: 
 <CAHAmRctFQ0HEAwrfv-gY5D=PxEqMwP+YvHmz_SaL84WR4ZA+=w@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Thanks for the help, Idris. I checked all the confs you mentioned, and 
all is as it should be. jps gives me:

24226 Jps
24073 TaskTracker
23854 JobTracker
23780 DataNode
23921 NameNode
23995 SecondaryNameNode

So that looks good. A majority of this stuff is default as set by 
Cloudera. Any other ideas?

Eli

On 1/9/12 3:22 PM, Idris Ali wrote:
> Hi,
>
> Looks like problem in starting DFS and MR, can you run 'jps' and see if NN,
> DN, SNN, JT and TT are running,
>
> also make sure for pseudo-distributed mode, the following entries are
> present:
>
> 1. In core-site.xml
>   <property>
>      <name>fs.default.name</name>
>      <value>hdfs://localhost:8020</value>
>    </property>
>
>    <property>
>       <name>hadoop.tmp.dir</name>
>       <value><SOME TMP dir with Read/Write acces not system temp></value>
>    </property>
>    <property>
>
> 2.  In hdfs-site.xml
> <property>
>      <name>dfs.replication</name>
>      <value>1</value>
>    </property>
>    <property>
>       <name>dfs.permissions</name>
>       <value>false</value>
>    </property>
>    <property>
>       <!-- specify this so that running 'hadoop namenode -format' formats
> the right dir -->
>       <name>dfs.name.dir</name>
>       <value>Local dir with Read/Write access</value>
>    </property>
>
> 3. In mapred-stie.xml
>    <property>
>      <name>mapred.job.tracker</name>
>      <value>localhost:8021</value>
>    </property>
>
> Thanks,
> -Idris
>
> On Tue, Jan 10, 2012 at 1:07 AM, Eli Finkelshteyn<iefinkel@gmail.com>wrote:
>
>> Positive. Like I said before, netstat -a | grep 8020 gives me nothing.
>> Even if the firewall was the problem, that should still give me output that
>> the port is listening, but I'd just be unable to hit it from an outside box
>> (I tested this by blocking port 50070, at which point it still showed up in
>> netstat -a, but was inaccessible through http from a remote machine). This
>> problem is something else.
>>
>>
>> On 1/9/12 2:31 PM, zGreenfelder wrote:
>>
>>> On Mon, Jan 9, 2012 at 1:58 PM, Eli Finkelshteyn<iefinkel@gmail.**com<iefinkel@gmail.com>>
>>>   wrote:
>>>
>>>> More info:
>>>>
>>>> In the DataNode log, I'm also seeing:
>>>>
>>>> 2012-01-09 13:06:27,751 INFO org.apache.hadoop.ipc.Client: Retrying
>>>> connect
>>>> to server: localhost/127.0.0.1:8020. Already tried 9 time(s).
>>>>
>>>> Why would things just not load on port 8020? I feel like all the errors
>>>> I'm
>>>> seeing are caused by this, but I can't see any errors about why this
>>>> occurred in the first place.
>>>>
>>>>   are you sure there isn't a firewall in place blocking port 8020?
>>> e.g. iptables on the local machines?   if you do
>>> telnet localhost 8020
>>> do you make a connection? if you use lsof and/or netstat can you see
>>> the port open?
>>> if you have root access you can try turning off the firewall with
>>> iptables -F to see if things work without firewall rules.
>>>
>>