Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
MapReduce >> mail # user >>


Hi,
CDH-Namenode by default listens in port 8020.
Try
hadoop fs -put /opt/test hdfs://192.168.10.22:8020/user/test
If you get the same message, then open the Namenode WebUI(http://192.168.10.22:50070). In the top, you can see the internal port.Then try to connect using that port.
 
Regards,
Jeba
________________________________
 From: shashwat shriparv <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Wednesday, 26 June 2013 6:37 PM
Subject: Re:
 
When you see this, it basically means that you are unable to connected
to the NameNode. It's either not running or running on a different port. please show us your core-site.xml

Thanks & Regards           
∞Shashwat Shriparv

On Wed, Jun 26, 2013 at 5:44 PM, Mohammad Tariq <[EMAIL PROTECTED]> wrote:

Or show the logs to us.
>
>
>Warm Regards,
>Tariq
>cloudfront.blogspot.com
>
>
>
>
>On Wed, Jun 26, 2013 at 2:03 PM, Devaraj k <[EMAIL PROTECTED]> wrote:
>
>Could you check the logs for the hadoop processes, are they started successfully or any problem while starting?
>> 
>>Thanks
>>Devaraj k
>> 
>>From:ch huang [mailto:[EMAIL PROTECTED]]
>>Sent: 26 June 2013 12:38
>>To: [EMAIL PROTECTED]
>>Subject:
>> 
>>hi i build a new hadoop cluster ,but i can not ACCESS hdfs ,why? i use CDH3u4 ,redhat6.2
>> 
>># hadoop fs -put /opt/test hdfs://192.168.10.22:9000/user/test
>>13/06/26 15:00:47 INFO ipc.Client: Retrying connect to server: /192.168.10.22:9000. Already tried 0 time(s).
>>13/06/26 15:00:48 INFO ipc.Client: Retrying connect to server: /192.168.10.22:9000. Already tried 1 time(s).
>>13/06/26 15:00:49 INFO ipc.Client: Retrying connect to server: /192.168.10.22:9000. Already tried 2 time(s).
>>13/06/26 15:00:50 INFO ipc.Client: Retrying connect to server: /192.168.10.22:9000. Already tried 3 time(s).
>>13/06/26 15:00:51 INFO ipc.Client: Retrying connect to server: /192.168.10.22:9000. Already tried 4 time(s).
>>13/06/26 15:00:52 INFO ipc.Client: Retrying connect to server: /192.168.10.22:9000. Already tried 5 time(s).
>>13/06/26 15:00:53 INFO ipc.Client: Retrying connect to server: /192.168.10.22:9000. Already tried 6 time(s).
>>13/06/26 15:00:54 INFO ipc.Client: Retrying connect to server: /192.168.10.22:9000. Already tried 7 time(s).
>>13/06/26 15:00:55 INFO ipc.Client: Retrying connect to server: /192.168.10.22:9000. Already tried 8 time(s).
>>13/06/26 15:00:56 INFO ipc.Client: Retrying connect to server: /192.168.10.22:9000. Already tried 9 time(s).
>>put: Call to /192.168.10.22:9000 failed on connection exception: java.net.ConnectException: Connection refused
>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB