Sign up ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

I have given the path for both the configuration files directory and the .sh files directory.

I managed to do the configurations with this path:

root@ratan-Inspiron-N5110:/home/hduser/hadoop/hadoop-2.4.0/etc/hadoop# gedit coresite.xml


<!-- In: conf/core-site.xml -->
  <description>A base for other temporary directories.</description>

  <description>The name of the default file system.  A URI whose
  scheme and authority determine the FileSystem implementation.  The
  uri's scheme determines the config property (fs.SCHEME.impl) naming
  the FileSystem implementation class.  The uri's authority is used to
  determine the host, port, etc. for a filesystem.</description>


root@ratan-Inspiron-N5110:/home/hduser/hadoop/hadoop-2.4.0/etc/hadoop# gedit mapred-site.xml


 <!-- In: conf/mapred-site.xml -->
  <description>The host and port that the MapReduce job tracker runs
  at.  If "local", then jobs are run in-process as a single map
  and reduce task.


root@ratan-Inspiron-N5110:/home/hduser/hadoop/hadoop-2.4.0/etc/hadoop# gedit hdfs-site.xml


 <!-- In: conf/hdfs-site.xml -->
  <description>Default block replication.
  The actual number of replications can be specified when the file is created.
  The default is used if replication is not specified in create time.


My directory details:

hduser@ratan-Inspiron-N5110:~/hadoop/hadoop-2.4.0/etc$ cd ./hadoop
hduser@ratan-Inspiron-N5110:~/hadoop/hadoop-2.4.0/etc/hadoop$ ls
capacity-scheduler.xml      hadoop-policy.xml        mapred-queues.xml.template
configuration.xsl           hdfs-site.xml            mapred-site.xml
container-executor.cfg      hdfs-site.xml~           mapred-site.xml~
core-site.xml                 mapred-site.xml.template
core-site.xml~      slaves
hadoop-env.cmd              httpfs-signature.secret  ssl-client.xml.example               httpfs-site.xml          ssl-server.xml.example             yarn-env.cmd  mapred-env.cmd             yarn-site.xml
hduser@ratan-Inspiron-N5110:~/hadoop/hadoop-2.4.0/etc/hadoop$ cd ..
hduser@ratan-Inspiron-N5110:~/hadoop/hadoop-2.4.0/etc$ ls

hduser@ratan-Inspiron-N5110:~/hadoop/hadoop-2.4.0/etc$ cd ..
hduser@ratan-Inspiron-N5110:~/hadoop/hadoop-2.4.0$ ls
bin  etc  include  lib  libexec  LICENSE.txt  logs  NOTICE.txt  README.txt  sbin  share
hduser@ratan-Inspiron-N5110:~/hadoop/hadoop-2.4.0$ cd ./etc
hduser@ratan-Inspiron-N5110:~/hadoop/hadoop-2.4.0/etc$ ls
hduser@ratan-Inspiron-N5110:~/hadoop/hadoop-2.4.0/etc$ cd ..
hduser@ratan-Inspiron-N5110:~/hadoop/hadoop-2.4.0$ cd ./sbin
hduser@ratan-Inspiron-N5110:~/hadoop/hadoop-2.4.0/sbin$ ls           start-dfs.cmd     stop-dfs.cmd                start-all.cmd  
hdfs-config.cmd  start-yarn.cmd  stop-yarn.cmd

When I start the daemons:

hduser@ratan-Inspiron-N5110:~/hadoop/hadoop-2.4.0/sbin$ ls    start-all.cmd    stop-dfs.cmd
hdfs-config.cmd          start-dfs.cmd         stop-yarn.cmd  start-yarn.cmd                stop-all.cmd
hduser@ratan-Inspiron-N5110:~/hadoop/hadoop-2.4.0/sbin$ ./
This script is Deprecated. Instead use and
Starting namenodes on [localhost]
localhost: starting namenode, logging to /home/hduser/hadoop/hadoop-2.4.0/logs/hadoop-hduser-namenode-ratan-Inspiron-N5110.out
localhost: starting datanode, logging to /home/hduser/hadoop/hadoop-2.4.0/logs/hadoop-hduser-datanode-ratan-Inspiron-N5110.out
Starting secondary namenodes [] starting secondarynamenode, logging to /home/hduser/hadoop/hadoop-2.4.0/logs/hadoop-hduser-secondarynamenode-ratan-Inspiron-N5110.out
starting yarn daemons
starting resourcemanager, logging to /home/hduser/hadoop/hadoop-2.4.0/logs/yarn-hduser-resourcemanager-ratan-Inspiron-N5110.out
localhost: starting nodemanager, logging to /home/hduser/hadoop/hadoop-2.4.0/logs/yarn-hduser-nodemanager-ratan-Inspiron-N5110.out
hduser@ratan-Inspiron-N5110:~/hadoop/hadoop-2.4.0/sbin$ jps

1441 DataNode
1608 SecondaryNameNode
1912 NodeManager
2448 Jps
1775 ResourceManager


The problem is I cannot find the namenode that has to be formatted. And when I run the daemons, the namenode is nowhere to be seen. Where am I going wrong?

share|improve this question
I have the same problem when I installed hadoop-2.4.0, now I have installed hadoop-1.0.3, Its working properly.. I thing the configuration not proper for latest version... –  ARUL Jun 17 '14 at 11:46

2 Answers 2

Check this log file:


If it says namenode is not formatted, format it

bin/hadoop namenode -format

share|improve this answer

Check the Storage directory exist or not if yes check the permissions and format the namenode than restrt dfs.It will work..


share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.