On Sat, Apr 4, 2009 at 6:46 PM, Foss User <[email protected]> wrote: > Whenever I try to start the DFS, I get this error: > > had...@namenode:~/hadoop-0.19.1$ bin/start-dfs.sh > starting namenode, logging to > /home/hadoop/hadoop-0.19.1/bin/../logs/hadoop-hadoop-namenode-hadoop-namenode.out > 10.31.253.142: starting datanode, logging to > /home/hadoop/hadoop-0.19.1/bin/../logs/hadoop-hadoop-datanode-hadoop-slave-a.out > 10.31.253.146: starting datanode, logging to > /home/hadoop/hadoop-0.19.1/bin/../logs/hadoop-hadoop-datanode-hadoop-slave-b.out > 10.31.253.135: starting secondarynamenode, logging to > /home/hadoop/hadoop-0.19.1/bin/../logs/hadoop-hadoop-secondarynamenode-hadoop-jobtracker.out > 10.31.253.130: starting secondarynamenode, logging to > /home/hadoop/hadoop-0.19.1/bin/../logs/hadoop-hadoop-secondarynamenode-hadoop-namenode.out > 10.31.253.135: Exception in thread "main" java.lang.NullPointerException > 10.31.253.135: at > org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:132) > 10.31.253.135: at > org.apache.hadoop.hdfs.server.namenode.NameNode.getAddress(NameNode.java:130) > 10.31.253.135: at > org.apache.hadoop.hdfs.server.namenode.NameNode.getAddress(NameNode.java:134) > 10.31.253.135: at > org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.initialize(SecondaryNameNode.java:131) > 10.31.253.135: at > org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.<init>(SecondaryNameNode.java:115) > 10.31.253.135: at > org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.main(SecondaryNameNode.java:469) > > What could be the problem? > > 10.31.253.130 is the namenode > 10.31.253.135 is the job tracker >
I am replying my own question here as I figured out the solution. The hadoop-site.xml in the job tracker was not configured. After configuring it, this got resolved.
