Hi friends, I have been trying to start hadoop on the master but it doesn't start the name node on it, checking the logs I found the following error
2008-03-11 11:47:07,371 INFO org.apache.hadoop.dfs.NameNode: STARTUP_MSG: /************************************************************ STARTUP_MSG: Starting NameNode STARTUP_MSG: host = ved-desktop/192.168.0.52 STARTUP_MSG: args = [] STARTUP_MSG: version = 0.16.0 STARTUP_MSG: build = http://svn.apache.org/repos/asf/hadoop/core/branches/branch-0.16 -r 618351; compiled by 'hadoopqa' on Mon Feb 4 19:29:11 UTC 2008 ************************************************************/ 2008-03-11 11:47:07,633 INFO org.apache.hadoop.metrics.jvm.JvmMetrics: Initializing RPC Metrics with serverName=NameNode, port=50001 2008-03-11 11:47:07,646 INFO org.apache.hadoop.dfs.NameNode: Namenode up at: ved-desktop/192.168.0.52:50001 2008-03-11 11:47:07,652 INFO org.apache.hadoop.metrics.jvm.JvmMetrics: Initializing JVM Metrics with processName=NameNode, sessionId=null 2008-03-11 11:47:07,740 INFO org.apache.hadoop.dfs.NameNodeMetrics: Initializing NameNodeMeterics using context object: org.apache.hadoop.metrics.spi.NullContext 2008-03-11 11:47:07,944 INFO org.apache.hadoop.fs.FSNamesystem: fsOwner=root,root 2008-03-11 11:47:07,945 INFO org.apache.hadoop.fs.FSNamesystem: supergroup=supergroup 2008-03-11 11:47:07,945 INFO org.apache.hadoop.fs.FSNamesystem: isPermissionEnabled=true 2008-03-11 11:47:08,234 INFO org.apache.hadoop.fs.FSNamesystem: Finished loading FSImage in 413 msecs 2008-03-11 11:47:08,239 INFO org.apache.hadoop.fs.FSNamesystem: Leaving safemode after 417 msecs 2008-03-11 11:47:08,239 INFO org.apache.hadoop.dfs.StateChange: STATE* Network topology has 0 racks and 0 datanodes 2008-03-11 11:47:08,239 INFO org.apache.hadoop.dfs.StateChange: STATE* UnderReplicatedBlocks has 0 blocks 2008-03-11 11:47:08,355 INFO org.apache.hadoop.fs.FSNamesystem: Registered FSNamesystemStatusMBean 2008-03-11 11:47:08,370 ERROR org.apache.hadoop.dfs.NameNode: java.lang.RuntimeException: Not a host:port pair: 50004 at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java :110) at org.apache.hadoop.dfs.FSNamesystem.initialize(FSNamesystem.java :282) at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:235) at org.apache.hadoop.dfs.NameNode.initialize(NameNode.java:130) at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:175) at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:161) at org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:843) at org.apache.hadoop.dfs.NameNode.main(NameNode.java:852) 2008-03-11 11:47:08,371 INFO org.apache.hadoop.dfs.NameNode: SHUTDOWN_MSG: /************************************************************ SHUTDOWN_MSG: Shutting down NameNode at ved-desktop/192.168.0.52 ************************************************************/ hadoop-site.xml listing <configuration> <property> <name>mapred.child.java.opts</name> <value>-Xmx1024m -verbose:gc -Xloggc:/tmp/@[EMAIL PROTECTED]</value> <description>Java opts for the task tracker child processes. Subsumes 'mapred.child.heap.size' (If a mapred.child.heap.size value is found in a configuration, its maximum heap size will be used and a warning emitted that heap.size has been deprecated). Also, the following symbol, if present, will be interpolated: @taskid@ is replaced by current TaskID. Any other occurrences of '@' will go unchanged. For example, to enable verbose gc logging to a file named for the taskid in /tmp and to set the heap maximum to be a gigabyte, pass a 'value' of: -Xmx1024m -verbose:gc -Xloggc:/tmp/@[EMAIL PROTECTED] </description> </property> <property> <name>fs.default.name</name> <value>hdfs://ved-desktop:50001</value> </property> <property> <name>mapred.job.tracker</name> <value>ved-desktop:50002</value> </property> <property> <name>dfs.name.dir</name> <value>/usr/local/hadoop-data</value> </property> <property> <name>dfs.replication</name> <value>2</value> </property> <property> <name>dfs.secondary.http.address</name> <value>50003</value> </property> <property> <name>dfs.http.address</name> <value>50004</value> </property> <property> <name>mapred.job.tracker.http.address</name> <value>50005</value> </property> <property> <name>tasktracker.http.address</name> <value>50006</value> </property> </configuration> Yesterday I could start namenode, tasktracker, jobtracker, secondarynamenode properly but today its giving me problem. What could be the reason, can anyone help me with this? Thanks
