hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-4871) SE
Date Tue, 16 Dec 2008 10:38:44 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Douglas resolved HADOOP-4871.
-----------------------------------

    Resolution: Invalid

Dino-

You should ping the [mailing list|http://hadoop.apache.org/core/mailing_lists.html], look
through the [archives|http://mail-archives.apache.org/mod_mbox/hadoop-core-user/], or try
the [quickstart|http://hadoop.apache.org/core/docs/r0.17.2/quickstart.html] rather than filing
a bug.

Good luck.

> SE
> --
>
>                 Key: HADOOP-4871
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4871
>             Project: Hadoop Core
>          Issue Type: Task
>    Affects Versions: 0.17.1
>         Environment: Ubuntu 8.04
>            Reporter: Dino M. Amaral
>
> I got 3 hosts in the cluster : one for master 172.18.30.149 and the others as slaves
(172.18.30.137 e 172.18.30.153). When i try to start, i got the following error. When i configure
the masters file, and try 172.18.30.137, the secondary namenode starts. 
> I think the problem is at master (172.18.30.149), cause this host doesn´t start neither
Namenode nor secondary NameNode.
> Cloud anyone give me a hand ????
> hadoop@cloud-cos001:/tmp/hadoop$ bin/start-dfs.sh 
> starting namenode, logging to /tmp/hadoop/bin/../logs/hadoop-hadoop-namenode-cloud-cos001.out
> 172.18.30.137: datanode running as process 23598. Stop it first.
> 172.18.30.153: datanode running as process 19379. Stop it first.
> 172.18.30.149: starting datanode, logging to /tmp/hadoop/bin/../logs/hadoop-hadoop-datanode-cloud-cos001.out
> 172.18.30.149: starting secondarynamenode, logging to /tmp/hadoop/bin/../logs/hadoop-hadoop-secondarynamenode-cloud-cos001.out
> 172.18.30.149: Exception in thread "main" java.lang.NullPointerException
> 172.18.30.149:  at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:119)
> 172.18.30.149:  at org.apache.hadoop.dfs.SecondaryNameNode.<init>(SecondaryNameNode.java:118)
> 172.18.30.149:  at org.apache.hadoop.dfs.SecondaryNameNode.main(SecondaryNameNode.java:495)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message