Hadoop 2.2.0版本./start-all.sh错误解决
博客专区 > mskk 的博客 > 博客详情
Hadoop 2.2.0版本./start-all.sh错误解决
mskk 发表于7个月前
Hadoop 2.2.0版本./start-all.sh错误解决
  • 发表于 7个月前
  • 阅读 0
  • 收藏 0
  • 点赞 0
  • 评论 0

腾讯云 新注册用户 域名抢购1元起>>>   

转自<http://www.lvcy.net/?post=162>

001 This script is Deprecated. Instead use start-dfs.sh and start-yarn.sh
002 Starting namenodes on [Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /home/hadoop/hadoop/lib/native/libhadoop.so.1.0.0 which might have disabled stack guard. The VM will try to fix the stack guard now.
003 It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.]
004 HotSpot(TM): ssh: Could not resolve hostname HotSpot(TM): Name or service not known
005 -c: Unknown cipher type 'cd'
006 64-Bit: ssh: Could not resolve hostname 64-Bit: Name or service not known
007 you: ssh: Could not resolve hostname you: Name or service not known
008 Server: ssh: Could not resolve hostname Server: Name or service not known
009 You: ssh: Could not resolve hostname You: Name or service not known
010 The: ssh: Could not resolve hostname The: Name or service not known
011 Java: ssh: Could not resolve hostname Java: Name or service not known
012 will: ssh: Could not resolve hostname will: Name or service not known
013 guard.: ssh: Could not resolve hostname guard.: Name or service not known
014 stack: ssh: Could not resolve hostname stack: Name or service not known
015 disabled: ssh: Could not resolve hostname disabled: Name or service not known
016 with: ssh: Could not resolve hostname with: Name or service not known
017 highly: ssh: Could not resolve hostname highly: Name or service not known
018 guard: ssh: Could not resolve hostname guard: Name or service not known
019 recommended: ssh: Could not resolve hostname recommended: Name or service not known
020 whichssh: Could not resolve hostname which: Name or service not known
021 it: ssh: Could not resolve hostname it: Name or service not known
022 It's: ssh: Could not resolve hostname It's: Name or service not known
023 have: ssh: Could not resolve hostname have: Name or service not known
024 fix: ssh: Could not resolve hostname fix: Name or service not known
025 or: ssh: Could not resolve hostname or: Name or service not known
026 VM: ssh: Could not resolve hostname VM: Name or service not known
027 now.: ssh: Could not resolve hostname now.: Name or service not known
028 try: ssh: Could not resolve hostname try: Name or service not known
029 stack: ssh: Could not resolve hostname stack: Name or service not known
030 library: ssh: Could not resolve hostname library: Name or service not known
031 <libfile>',: ssh: Could not resolve hostname <libfile>',: Name or service not known
032 might: ssh: Could not resolve hostname might: Name or service not known
033 noexecstack'.: ssh: Could not resolve hostname noexecstack'.: Name or service not known
034 have: ssh: Could not resolve hostname have: Name or service not known
035 'execstack: ssh: Could not resolve hostname 'execstack: Name or service not known
036 fix: ssh: Could not resolve hostname fix: Name or service not known
037 link: ssh: Could not resolve hostname link: Name or service not known
038 warning:: ssh: Could not resolve hostname warning:: Name or service not known
039 with: ssh: Could not resolve hostname with: Name or service not known
040 that: ssh: Could not resolve hostname that: Name or service not known
041 the: ssh: Could not resolve hostname the: Name or service not known
042 VM: ssh: Could not resolve hostname VM: Name or service not known
043 loaded: ssh: Could not resolve hostname loaded: Name or service not known
044 '-z: ssh: Could not resolve hostname '-z: Name or service not known
045 the: ssh: Could not resolve hostname the: Name or service not known
046 library: ssh: Could not resolve hostname library: Name or service not known
047 to: ssh: connect to host to port 22: Connection refused
048 localhost: Error: JAVA_HOME is not set and could not be found.
049 Starting secondary namenodes [Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /home/hadoop/hadoop/lib/native/libhadoop.so.1.0.0 which might have disabled stack guard. The VM will try to fix the stack guard now.
050 It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
051 0.0.0.0]
052 Java: ssh: Could not resolve hostname Java: Name or service not known
053 HotSpot(TM): ssh: Could not resolve hostname HotSpot(TM): Name or service not known
054 Server: ssh: Could not resolve hostname Server: Name or service not known
055 64-Bit: ssh: Could not resolve hostname 64-Bit: Name or service not known
056 VM: ssh: Could not resolve hostname VM: Name or service not known
057 -c: Unknown cipher type 'cd'
058 You: ssh: Could not resolve hostname You: Name or service not known
059 have: ssh: Could not resolve hostname have: Name or service not known
060 that: ssh: Could not resolve hostname that: Name or service not known
061 warning:: ssh: Could not resolve hostname warning:: Name or service not known
062 loaded: ssh: Could not resolve hostname loaded: Name or service not known
063 stack: ssh: Could not resolve hostname stack: Name or service not known
064 the: ssh: Could not resolve hostname the: Name or service not known
065 fix: ssh: Could not resolve hostname fix: Name or service not known
066 library: ssh: Could not resolve hostname library: Name or service not known
067 with: ssh: Could not resolve hostname with: Name or service not known
068 stack: ssh: Could not resolve hostname stack: Name or service not known
069 have: ssh: Could not resolve hostname have: Name or service not known
070 try: ssh: Could not resolve hostname try: Name or service not known
071 recommended: ssh: Could not resolve hostname recommended: Name or service not known
072 It's: ssh: Could not resolve hostname It's: Name or service not known
073 might: ssh: Could not resolve hostname might: Name or service not known
074 the: ssh: Could not resolve hostname the: Name or service not known
075 now.: ssh: Could not resolve hostname now.: Name or service not known
076 disabled: ssh: Could not resolve hostname disabled: Name or service not known
077 highly: ssh: Could not resolve hostname highly: Name or service not known
078 VM: ssh: Could not resolve hostname VM: Name or service not known
079 fix: ssh: Could not resolve hostname fix: Name or service not known
080 'execstack: ssh: Could not resolve hostname 'execstack: Name or service not known
081 whichssh: Could not resolve hostname which: Name or service not known
082 you: ssh: Could not resolve hostname you: Name or service not known
083 will: ssh: Could not resolve hostname will: Name or service not known
084 guard: ssh: Could not resolve hostname guard: Name or service not known
085 noexecstack'.: ssh: Could not resolve hostname noexecstack'.: Name or service not known
086 <libfile>',: ssh: Could not resolve hostname <libfile>',: Name or service not known
087 link: ssh: Could not resolve hostname link: Name or service not known
088 or: ssh: Could not resolve hostname or: Name or service not known
089 The: ssh: Could not resolve hostname The: Name or service not known
090 library: ssh: Could not resolve hostname library: Name or service not known
091 with: ssh: Could not resolve hostname with: Name or service not known
092 it: ssh: Could not resolve hostname it: Name or service not known
093 guard.: ssh: Could not resolve hostname guard.: Name or service not known
094 '-z: ssh: Could not resolve hostname '-z: Name or service not known
095 to: ssh: connect to host to port 22: Connection refused
096 0.0.0.0: Error: JAVA_HOME is not set and could not be found.
097 starting yarn daemons
098 starting resourcemanager, logging to /home/hadoop/hadoop/logs/yarn-hadoop-resourcemanager-master.out
099 Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library /home/hadoop/hadoop/lib/native/libhadoop.so.1.0.0 whichmight have disabled stack guard. The VM will try to fix the stack guard now.
100 It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
101 localhost: Error: JAVA_HOME is not set and could not be found.

 

解决办法一:

hadoop@master~: sudo gedit ~/.bash_profile    然后输入如下内容并保存:

 

1 export HADOOP_COMMON_LIB_NATIVE_DIR=${HADOOP_PREFIX}/lib/native
2 export HADOOP_OPTS="-Djava.library.path=$HADOOP_PREFIX/lib"

解决办法二:

 

打开$HADOOP_HOME/etc/hadoop/hadoop-env.sh文件,输入如下内容并保存

 

1 export HADOOP_COMMON_LIB_NATIVE_DIR=${HADOOP_PREFIX}/lib/native
2 export HADOOP_OPTS="-Djava.library.path=$HADOOP_PREFIX/lib"

解决办法三:

 

打开$HADOOP_HOME/etc/hadoop/yarn-env.sh,在任意位置输入如下内容

 

1 export HADOOP_COMMON_LIB_NATIVE_DIR=${HADOOP_PREFIX}/lib/native
2 export HADOOP_OPTS="-Djava.library.path=$HADOOP_PREFIX/lib"

最后在运行$HADOOP_HOME/sbin/start-all.sh

标签: hadoop
共有 人打赏支持
粉丝 3
博文 138
码字总数 2246
×
mskk
如果觉得我的文章对您有用,请随意打赏。您的支持将鼓励我继续创作!
* 金额(元)
¥1 ¥5 ¥10 ¥20 其他金额
打赏人
留言
* 支付类型
微信扫码支付
打赏金额:
已支付成功
打赏金额: