hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bibek Paudel <eternalyo...@gmail.com>
Subject Re: Namenode trying to connect to localhost instead of the name and dying
Date Wed, 02 Mar 2011 23:09:54 GMT
On Thu, Mar 3, 2011 at 12:08 AM, Eric Sammer <esammer@cloudera.com> wrote:
> Check your /etc/hosts file and make sure the hostname of the machine is not
> on the loopback device. This is almost always the cause of this.
>

+1

-b

> On Wed, Mar 2, 2011 at 5:57 PM, Mark Kerzner <markkerzner@gmail.com> wrote:
>
>> Hi,
>>
>> I am doing a pseudo-distributed mode on my laptop, following the same steps
>> I used for all configurations on my regular cluster, but I get this error
>>
>> 2011-03-02 16:45:13,651 INFO
>> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit: ugi=mapred ip=/
>> 192.168.1.150 cmd=delete
>> src=/var/lib/hadoop-0.20/cache/mapred/mapred/system/jobtracker.infodst=null
>> perm=null
>> 2011-03-02 16:45:14,524 INFO org.apache.hadoop.ipc.Client: Retrying connect
>> to server: ubuntu/127.0.1.1:8020. Already tried 0 time(s).
>>
>> so it should be connecting to 192.168.1.150, and it is instead connecting
>> to
>> 127.0.1.1 - where does this ip come from?
>>
>> Thank you,
>> Mark
>>
>
>
>
> --
> Eric Sammer
> twitter: esammer
> data: www.cloudera.com
>

Mime
View raw message