jps listing is not showing namenode daemon. Verify why namenode is not up from the logs.
On 4/27/15, Anand Murali <anand_vi...@yahoo.com> wrote: > Dear All: > > Please find below. > > and_vihar@Latitude-E5540:~/hadoop-2.6.0/sbin$ > start-dfs.sh > > Starting namenodes on [localhost] > localhost: starting namenode, logging to > /home/anand_vihar/hadoop-2.6.0/logs/hadoop-anand_vihar-namenode-Latitude-E5540.out > localhost: starting datanode, logging to > /home/anand_vihar/hadoop-2.6.0/logs/hadoop-anand_vihar-datanode-Latitude-E5540.out > Starting secondary namenodes [0.0.0.0] > 0.0.0.0: starting secondarynamenode, logging to > /home/anand_vihar/hadoop-2.6.0/logs/hadoop-anand_vihar-secondarynamenode-Latitude-E5540.out > anand_vihar@Latitude-E5540:~/hadoop-2.6.0/sbin$ start-yarn.sh > starting yarn daemons > starting resourcemanager, logging to > /home/anand_vihar/hadoop-2.6.0/logs/yarn-anand_vihar-resourcemanager-Latitude-E5540.out > localhost: starting nodemanager, logging to > /home/anand_vihar/hadoop-2.6.0/logs/yarn-anand_vihar-nodemanager-Latitude-E5540.out > anand_vihar@Latitude-E5540:~/hadoop-2.6.0/sbin$ jps > 7464 Jps > 7147 NodeManager > 6863 SecondaryNameNode > 7017 ResourceManager > 6686 DataNode > anand_vihar@Latitude-E5540:~/hadoop-2.6.0/sbin$ hdfs dfs -ls > ls: Call From Latitude-E5540/127.0.1.1 to localhost:9000 failed on > connection exception: java.net.ConnectException: Connection refused; For > more details see: http://wiki.apache.org/hadoop/ConnectionRefused > > Has anybody encountered this error and fixed it. I have checked > http://wiki.apache.org/hadoop/ConnectionRefused but there is no information > on how to fix it. It is obvious that it seems to be a network error , but I > am interested in knowing if anybody has faced this error and fixed it. Reply > and help most appreciated. > > Thanks > > Regards, Anand Murali 11/7, 'Anand Vihar', Kandasamy St, MylaporeChennai - > 600 004, IndiaPh: (044)- 28474593/ 43526162 (voicemail)
