Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 29 Aug 2011 04:32:37 +0000 (UTC)
From: "Uma Maheswara Rao G (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <650089634.2170.1314592357760.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1125222973.2098.1314589837862.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2295) Call to localhost/127.0.0.1:54310
 failed on connection exception: Connection refused
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092630#comment-13092630 ] 

Uma Maheswara Rao G commented on HDFS-2295:
-------------------------------------------

Hi Patrik,
Did you check, whether your namenode started successfully?

I think, this kind of things  can be post into mailing list instead of raising in JIRA.
JIRA is mainly to track confirmed bugs.

Thanks,
Uma

> Call to localhost/127.0.0.1:54310 failed on connection exception: Connection refused
> ------------------------------------------------------------------------------------
>
>                 Key: HDFS-2295
>                 URL: https://issues.apache.org/jira/browse/HDFS-2295
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node, hdfs client, name-node
>    Affects Versions: 0.20.2
>         Environment: Ubuntu 11.04 64bit , hadoop 0.20.2
>            Reporter: patrick.J
>              Labels: hadoop
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> when I try it
> dm@master:/usr/local/hadoop-0.20.2$ bin/hadoop dfs -ls hdfs://localhost:54310/
> It cast these exceptions
> 11/08/29 11:34:29 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 0 time(s).
> 11/08/29 11:34:30 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 1 time(s).
> 11/08/29 11:34:31 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 2 time(s).
> 11/08/29 11:34:32 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 3 time(s).
> 11/08/29 11:34:33 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 4 time(s).
> 11/08/29 11:34:34 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 5 time(s).
> 11/08/29 11:34:35 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 6 time(s).
> 11/08/29 11:34:36 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 7 time(s).
> 11/08/29 11:34:37 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 8 time(s).
> 11/08/29 11:34:38 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:54310. Already tried 9 time(s).
> ls: Call to localhost/127.0.0.1:54310 failed on connection exception: java.net.ConnectException: Connection refused
> Our namenode is listening to the 54310 port.
> <name>fs.default.name</name>
> <value>hdfs://master:54310</value>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira