sun java is the preferable choice for running hadoop properly. Regards, Mohammad Tariq
On Tue, Jun 19, 2012 at 3:10 PM, soham sardar <[email protected]> wrote: > Hey yogesh , > Thanks for the suggestion but it didnt help me a lot , > i am able to start my resourcemanager and nodemanger by > > ./yarn-daemon.sh start resourcemanager > ./yarn-daemon.sh start nodemanager > > and the jps output is > 14953 Jps > 13430 ResourceManager > 13667 NodeManager > > > now when i try to start the ./start-all.sh file it gives the following error > > its trying to create dir's in the root like /hduser and for which its > not getting the permission and the start up process is failed can u > suggest me a way in which this could be avoided > > This script is Deprecated. Instead use start-dfs.sh and start-yarn.sh > Starting namenodes on [localhost] > localhost: mkdir: cannot create directory `/hduser': Permission denied > localhost: chown: cannot access `/hduser/hduser': No such file or directory > localhost: starting namenode, logging to > /hduser/hduser/hadoop-hduser-namenode-XPS-L501X.out > localhost: /home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/sbin/hadoop-daemon.sh: > line 150: /hduser/hduser/hadoop-hduser-namenode-XPS-L501X.out: No such > file or directory > localhost: head: cannot open > `/hduser/hduser/hadoop-hduser-namenode-XPS-L501X.out' for reading: No > such file or directory > localhost: mkdir: cannot create directory `/hduser': Permission denied > localhost: chown: cannot access `/hduser/hduser': No such file or directory > localhost: starting datanode, logging to > /hduser/hduser/hadoop-hduser-datanode-XPS-L501X.out > localhost: /home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/sbin/hadoop-daemon.sh: > line 150: /hduser/hduser/hadoop-hduser-datanode-XPS-L501X.out: No such > file or directory > localhost: head: cannot open > `/hduser/hduser/hadoop-hduser-datanode-XPS-L501X.out' for reading: No > such file or directory > Starting secondary namenodes [0.0.0.0] > 0.0.0.0: mkdir: cannot create directory `/hduser': Permission denied > 0.0.0.0: chown: cannot access `/hduser/hduser': No such file or directory > 0.0.0.0: starting secondarynamenode, logging to > /hduser/hduser/hadoop-hduser-secondarynamenode-XPS-L501X.out > 0.0.0.0: /home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/sbin/hadoop-daemon.sh: > line 150: /hduser/hduser/hadoop-hduser-secondarynamenode-XPS-L501X.out: > No such file or directory > 0.0.0.0: head: cannot open > `/hduser/hduser/hadoop-hduser-secondarynamenode-XPS-L501X.out' for > reading: No such file or directory > starting yarn daemons > resourcemanager running as process 13430. Stop it first. > localhost: nodemanager running as process 13667. Stop it first. > > > On Tue, Jun 19, 2012 at 1:46 PM, yogesh dhari <[email protected]> wrote: >> Hello Soham, >> >> Have you set the path in hadoop-env.sh for java? >> >> set the java path over there >> >> export JAVA_HOME=/usr/lib/jvm/java-6-openjdk >> >> >> Regards >> Yogesh Kumar >> >> >>> Date: Tue, 19 Jun 2012 13:34:42 +0530 >>> Subject: namenode startup problem .. >>> From: [email protected] >>> To: [email protected] >> >>> >>> I am using open jdk 6 and my java home is set as >>> >>> soham@XPS-L501X:~$ echo $JAVA_HOME >>> /usr/lib/jvm/java-6-openjdk >>> >>> And the error i am getting during starting the nodes is >>> >>> hduser@XPS-L501X:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/sbin$ >>> ./start-all.sh >>> >>> This script is Deprecated. Instead use start-dfs.sh and start-yarn.sh >>> Starting namenodes on [localhost] >>> localhost: Error: JAVA_HOME is not set and could not be found. >>> localhost: Error: JAVA_HOME is not set and could not be found. >>> Starting secondary namenodes [0.0.0.0] >>> 0.0.0.0: Error: JAVA_HOME is not set and could not be found. >>> starting yarn daemons >>> starting resourcemanager, logging to >>> >>> /home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/logs/yarn-hduser-resourcemanager-XPS-L501X.out >>> localhost: Error: JAVA_HOME is not set and could not be found. >>> >>> hduser@XPS-L501X:/home/soham/cloudera/hadoop-2.0.0-cdh4.0.0/sbin$ >>> ./start-dfs.sh >>> Starting namenodes on [localhost] >>> localhost: Error: JAVA_HOME is not set and could not be found. >>> localhost: Error: JAVA_HOME is not set and could not be found. >>> Starting secondary namenodes [0.0.0.0] >>> 0.0.0.0: Error: JAVA_HOME is not set and could not be found. >>> >>> >>> Now the question i would like to ask is >>> Is these errors due to the Openjdk ??\ >>> Should I have to shift to Sunjdk rather than open jdk ???
