-Re: Namenode trying to connect to localhost instead of the name and dying
Mark Kerzner 2011-03-02, 23:07
all other daemons are alive, but namenode daemon dying
On Wed, Mar 2, 2011 at 5:01 PM, Mark Kerzner <[EMAIL PROTECTED]> wrote:
> It has just one entry
> ping hadoop-sony
> PING hadoop-sony (192.168.1.150) 56(84) bytes of data.
> 64 bytes from ubuntu (192.168.1.150): icmp_req=1 ttl=64 time=0.024 ms
> On Wed, Mar 2, 2011 at 4:59 PM, Bibek Paudel <[EMAIL PROTECTED]>wrote:
>> On Wed, Mar 2, 2011 at 11:57 PM, Mark Kerzner <[EMAIL PROTECTED]>
>> > Hi,
>> > I am doing a pseudo-distributed mode on my laptop, following the same
>> > I used for all configurations on my regular cluster, but I get this
>> > 2011-03-02 16:45:13,651 INFO
>> > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit: ugi=mapred
>> > 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
>> > 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?
>> My first reaction would be to check the conf/slaves file.
>> > Thank you,
>> > Mark