Created
October 25, 2013 13:29
-
-
Save ruo91/7154697 to your computer and use it in GitHub Desktop.
Hadoop 2.2.0 - warning: You have loaded library /home/hadoop/2.2.0/lib/native/libhadoop.so.1.0.0 which might have disabled stack guard.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| [hadoop@dev ~]$ start-all.sh | |
| This script is Deprecated. Instead use start-dfs.sh and start-yarn.sh | |
| 13/10/25 22:21:07 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable | |
| Starting namenodes on [Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /home/hadoop/2.2.0/lib/native/libhadoop.so.1.0.0 which might have disabled stack guard. The VM will try to fix the stack guard now. | |
| It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'. | |
| localhost] | |
| sed: -e expression #1, char 6: unknown option to `s' | |
| HotSpot(TM): ssh: Could not resolve hostname HotSpot(TM): Name or service not known | |
| 64-Bit: ssh: Could not resolve hostname 64-Bit: Name or service not known | |
| Java: ssh: Could not resolve hostname Java: Name or service not known | |
| Server: ssh: Could not resolve hostname Server: Name or service not known | |
| VM: ssh: Could not resolve hostname VM: Name or service not known | |
| You: ssh: Could not resolve hostname You: Name or service not known | |
| have: ssh: Could not resolve hostname have: Name or service not known | |
| loaded: ssh: Could not resolve hostname loaded: Name or service not known | |
| warning:: ssh: Could not resolve hostname warning:: Name or service not known | |
| library: ssh: Could not resolve hostname library: Name or service not known | |
| which: ssh: Could not resolve hostname which: Name or service not known | |
| disabled: ssh: Could not resolve hostname disabled: Name or service not known | |
| have: ssh: Could not resolve hostname have: Name or service not known | |
| might: ssh: Could not resolve hostname might: Name or service not known | |
| stack: ssh: Could not resolve hostname stack: Name or service not known | |
| VM: ssh: Could not resolve hostname VM: Name or service not known | |
| The: ssh: Could not resolve hostname The: Name or service not known | |
| will: ssh: Could not resolve hostname will: Name or service not known | |
| try: ssh: Could not resolve hostname try: Name or service not known | |
| fix: ssh: Could not resolve hostname fix: Name or service not known | |
| the: ssh: Could not resolve hostname the: Name or service not known | |
| to: ssh: Could not resolve hostname to: Name or service not known | |
| guard: ssh: Could not resolve hostname guard: Name or service not known | |
| It's: ssh: Could not resolve hostname It's: Name or service not known | |
| stack: ssh: Could not resolve hostname stack: Name or service not known | |
| highly: ssh: Could not resolve hostname highly: Name or service not known | |
| -c: Unknown cipher type 'cd' | |
| you: ssh: Could not resolve hostname you: Name or service not known | |
| that: ssh: Could not resolve hostname that: Name or service not known | |
| fix: ssh: Could not resolve hostname fix: Name or service not known | |
| recommended: ssh: Could not resolve hostname recommended: Name or service not known | |
| with: ssh: Could not resolve hostname with: Name or service not known | |
| the: ssh: Could not resolve hostname the: Name or service not known | |
| library: ssh: Could not resolve hostname library: Name or service not known | |
| 'execstack: ssh: Could not resolve hostname 'execstack: Name or service not known | |
| or: ssh: Could not resolve hostname or: Name or service not known | |
| <libfile>',: ssh: Could not resolve hostname <libfile>',: Name or service not known | |
| link: ssh: Could not resolve hostname link: Name or service not known | |
| with: ssh: Could not resolve hostname with: Name or service not known | |
| noexecstack'.: ssh: Could not resolve hostname noexecstack'.: Name or service not known | |
| it: ssh: Could not resolve hostname it: Name or service not known | |
| '-z: ssh: Could not resolve hostname '-z: Name or service not known | |
| localhost: starting namenode, logging to /home/hadoop/2.2.0/logs/hadoop-hadoop-namenode-dev.yongbok.net.out | |
| guard.: ssh: connect to host guard. port 30659: Connection timed out | |
| now.: ssh: connect to host now. port 30659: Connection timed out | |
| localhost: starting datanode, logging to /home/hadoop/2.2.0/logs/hadoop-hadoop-datanode-dev.yongbok.net.out | |
| Starting secondary namenodes [Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /home/hadoop/2.2.0/lib/native/libhadoop.so.1.0.0 which might have disabled stack guard. The VM will try to fix the stack guard now. | |
| It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'. | |
| 0.0.0.0] | |
| sed: -e expression #1, char 6: unknown option to `s' | |
| HotSpot(TM): ssh: Could not resolve hostname HotSpot(TM): Name or service not known | |
| 64-Bit: ssh: Could not resolve hostname 64-Bit: Name or service not known | |
| Server: ssh: Could not resolve hostname Server: Name or service not known | |
| warning:: ssh: Could not resolve hostname warning:: Name or service not known | |
| Java: ssh: Could not resolve hostname Java: Name or service not known | |
| You: ssh: Could not resolve hostname You: Name or service not known | |
| VM: ssh: Could not resolve hostname VM: Name or service not known | |
| have: ssh: Could not resolve hostname have: Name or service not known | |
| loaded: ssh: Could not resolve hostname loaded: Name or service not known | |
| library: ssh: Could not resolve hostname library: Name or service not known | |
| which: ssh: Could not resolve hostname which: Name or service not known | |
| have: ssh: Could not resolve hostname have: Name or service not known | |
| stack: ssh: Could not resolve hostname stack: Name or service not known | |
| disabled: ssh: Could not resolve hostname disabled: Name or service not known | |
| might: ssh: Could not resolve hostname might: Name or service not known | |
| VM: ssh: Could not resolve hostname VM: Name or service not known | |
| The: ssh: Could not resolve hostname The: Name or service not known | |
| will: ssh: Could not resolve hostname will: Name or service not known | |
| try: ssh: Could not resolve hostname try: Name or service not known | |
| to: ssh: Could not resolve hostname to: Name or service not known | |
| fix: ssh: Could not resolve hostname fix: Name or service not known | |
| stack: ssh: Could not resolve hostname stack: Name or service not known | |
| the: ssh: Could not resolve hostname the: Name or service not known | |
| guard: ssh: Could not resolve hostname guard: Name or service not known | |
| highly: ssh: Could not resolve hostname highly: Name or service not known | |
| It's: ssh: Could not resolve hostname It's: Name or service not known | |
| recommended: ssh: Could not resolve hostname recommended: Name or service not known | |
| that: ssh: Could not resolve hostname that: Name or service not known | |
| -c: Unknown cipher type 'cd' | |
| fix: ssh: Could not resolve hostname fix: Name or service not known | |
| you: ssh: Could not resolve hostname you: Name or service not known | |
| library: ssh: Could not resolve hostname library: Name or service not known | |
| the: ssh: Could not resolve hostname the: Name or service not known | |
| with: ssh: Could not resolve hostname with: Name or service not known | |
| 'execstack: ssh: Could not resolve hostname 'execstack: Name or service not known | |
| <libfile>',: ssh: Could not resolve hostname <libfile>',: Name or service not known | |
| or: ssh: Could not resolve hostname or: Name or service not known | |
| with: ssh: Could not resolve hostname with: Name or service not known | |
| link: ssh: Could not resolve hostname link: Name or service not known | |
| '-z: ssh: Could not resolve hostname '-z: Name or service not known | |
| it: ssh: Could not resolve hostname it: Name or service not known | |
| noexecstack'.: ssh: Could not resolve hostname noexecstack'.: Name or service not known | |
| 0.0.0.0: starting secondarynamenode, logging to /home/hadoop/2.2.0/logs/hadoop-hadoop-secondarynamenode-dev.yongbok.net.out | |
| guard.: ssh: connect to host guard. port 30659: Connection timed out | |
| now.: ssh: connect to host now. port 30659: Connection timed out | |
| 13/10/25 22:23:29 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable | |
| starting yarn daemons | |
| starting resourcemanager, logging to /home/hadoop/2.2.0/logs/yarn-hadoop-resourcemanager-dev.yongbok.net.out | |
| localhost: starting nodemanager, logging to /home/hadoop/2.2.0/logs/yarn-hadoop-nodemanager-dev.yongbok.net.out |
Its not worked for me even Im using 32 Bit Ubuntu 14.04
../bin/hadoop checknative -a
15/11/03 04:36:04 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
Native library checking:
hadoop: false
zlib: false
snappy: false
lz4: false
bzip2: false
openssl: false
15/11/03 04:36:05 INFO util.ExitUtil: Exiting with status 1
I followed this tutorial for hadoop cluster http://arturmkrtchyan.com/how-to-setup-multi-node-hadoop-2-yarn-cluster. I am getting the below mention error
15/11/04 18:34:51 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
Starting namenodes on [172.17.104.204]
after executing start-dfs.sh, then start-yarn.sh command is issued. Then
jps is showing in master node as given below
6602 Jps
6016 NameNode
6346 ResourceManager
6227 SecondaryNameNode
jps is showing in datanode as given below
2883 Jps
2639 DataNode
2758 NodeManager
if anyone knows please help me to solve this error. for this i look on stackoverflow and also ruo91 method for solving this then also getting same error
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks ...!! It works for resolving the issue related to a error,
" could not resolve localhost"
but still my datanode is not running....???
wat to do now