Hadoop 2.2.0版本./start-all.sh错误解决

最新推荐文章于 2022-08-31 14:21:00 发布

原创最新推荐文章于 2022-08-31 14:21:00 发布 · 385 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#hadoop

hadoop 专栏收录该内容

7 篇文章

订阅专栏

本文详细介绍了在使用Hadoop进行大数据处理时遇到的问题及其解决方案，包括如何配置环境变量、修复潜在的安全警告以及解决SSH连接问题等。通过遵循文中提供的步骤，读者可以顺利解决在部署和运行Hadoop集群时可能遇到的技术难题。

转自<http://www.lvcy.net/?post=162>
001This script is Deprecated. Instead use start-dfs.sh and start-yarn.sh
 
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. 

It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.] 

HotSpot(TM): ssh: Could not resolve hostname HotSpot(TM): Name or service not known 

-c: Unknown cipher type 'cd' 

64-Bit: ssh: Could not resolve hostname 64-Bit: Name or service not known 

you: ssh: Could not resolve hostname you: Name or service not known 

Server: ssh: Could not resolve hostname Server: Name or service not known 

You: ssh: Could not resolve hostname You: Name or service not known 

The: ssh: Could not resolve hostname The: Name or service not known 

Java: ssh: Could not resolve hostname Java: Name or service not known 

will: ssh: Could not resolve hostname will: Name or service not known 

guard.: ssh: Could not resolve hostname guard.: 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 

with: ssh: Could not resolve hostname with: Name or service not known 

highly: ssh: Could not resolve hostname highly: Name or service not known 

guard: ssh: Could not resolve hostname guard: Name or service not known 

recommended: ssh: Could not resolve hostname recommended: Name or service not known 

which: ssh: Could not resolve hostname which: Name or service not known 

it: ssh: Could not resolve hostname it: Name or service not known 

It's: ssh: Could not resolve hostname It's: Name or service not known 

have: ssh: Could not resolve hostname have: Name or service not known 

fix: ssh: Could not resolve hostname fix: Name or service not known 

or: ssh: Could not resolve hostname or: Name or service not known 

VM: ssh: Could not resolve hostname VM: Name or service not known 

now.: ssh: Could not resolve hostname now.: Name or service not known 

try: ssh: Could not resolve hostname try: Name or service not known 

stack: ssh: Could not resolve hostname stack: Name or service not known 

library: ssh: Could not resolve hostname library: Name or service not known 

<libfile>',: ssh: Could not resolve hostname <libfile>',: Name or service not known 

might: ssh: Could not resolve hostname might: Name or service not known 

noexecstack'.: ssh: Could not resolve hostname noexecstack'.: Name or service not known 

have: ssh: Could not resolve hostname have: Name or service not known 

'execstack: ssh: Could not resolve hostname 'execstack: Name or service not known 

fix: ssh: Could not resolve hostname fix: Name or service not known 

link: ssh: Could not resolve hostname link: Name or service not known 

warning:: ssh: Could not resolve hostname warning:: Name or service not known 

with: ssh: Could not resolve hostname with: Name or service not known 

that: ssh: Could not resolve hostname that: Name or service not known 

the: ssh: Could not resolve hostname the: Name or service not known 

VM: ssh: Could not resolve hostname VM: Name or service not known 

loaded: ssh: Could not resolve hostname loaded: Name or service not known 

'-z: ssh: Could not resolve hostname '-z: 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 

to: ssh: connect to host to port 22: Connection refused 

localhost: Error: JAVA_HOME is not set and could not be found. 

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. 

It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'. 

0.0.0]

Java: ssh: Could not resolve hostname Java: Name or service not known 

HotSpot(TM): ssh: Could not resolve hostname HotSpot(TM): Name or service not known 

Server: ssh: Could not resolve hostname Server: Name or service not known 

64-Bit: ssh: Could not resolve hostname 64-Bit: Name or service not known 

VM: ssh: Could not resolve hostname VM: Name or service not known 

-c: Unknown cipher type 'cd' 

You: ssh: Could not resolve hostname You: Name or service not known 

have: ssh: Could not resolve hostname have: Name or service not known 

that: ssh: Could not resolve hostname that: Name or service not known 

warning:: ssh: Could not resolve hostname warning:: Name or service not known 

loaded: ssh: Could not resolve hostname loaded: 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 

fix: ssh: Could not resolve hostname fix: Name or service not known 

library: ssh: Could not resolve hostname library: Name or service not known 

with: ssh: Could not resolve hostname with: Name or service not known 

stack: ssh: Could not resolve hostname stack: Name or service not known 

have: ssh: Could not resolve hostname have: Name or service not known 

try: ssh: Could not resolve hostname try: Name or service not known 

recommended: ssh: Could not resolve hostname recommended: Name or service not known 

It's: ssh: Could not resolve hostname It's: Name or service not known 

might: ssh: Could not resolve hostname might: Name or service not known 

the: ssh: Could not resolve hostname the: Name or service not known 

now.: ssh: Could not resolve hostname now.: Name or service not known 

disabled: ssh: Could not resolve hostname disabled: Name or service not known 

highly: ssh: Could not resolve hostname highly: Name or service not known 

VM: ssh: Could not resolve hostname VM: Name or service not known 

fix: ssh: Could not resolve hostname fix: Name or service not known 

'execstack: ssh: Could not resolve hostname 'execstack: Name or service not known 

which: ssh: Could not resolve hostname which: Name or service not known 

you: ssh: Could not resolve hostname you: Name or service not known 

will: ssh: Could not resolve hostname will: Name or service not known 

guard: ssh: Could not resolve hostname guard: Name or service not known 

noexecstack'.: ssh: Could not resolve hostname noexecstack'.: 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 

or: ssh: Could not resolve hostname or: 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 

with: ssh: Could not resolve hostname with: Name or service not known 

it: ssh: Could not resolve hostname it: Name or service not known 

guard.: ssh: Could not resolve hostname guard.: Name or service not known 

'-z: ssh: Could not resolve hostname '-z: Name or service not known 

to: ssh: connect to host to port 22: Connection refused 

0.0.0.0: Error: JAVA_HOME is not set and could not be found. 

    097starting yarn daemons

    098starting resourcemanager, logging to /home/hadoop/hadoop/logs/yarn-hadoop-resourcemanager-master.out

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. 

It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'. 

localhost: Error: JAVA_HOME is not set and could not be found.

解决办法一：

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

 
export HADOOP_COMMON_LIB_NATIVE_DIR=${HADOOP_PREFIX}/lib/native 

export HADOOP_OPTS="-Djava.library.path=$HADOOP_PREFIX/lib"

解决办法二：

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

 
export HADOOP_COMMON_LIB_NATIVE_DIR=${HADOOP_PREFIX}/lib/native 

export HADOOP_OPTS="-Djava.library.path=$HADOOP_PREFIX/lib"

解决办法三：

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

 
export HADOOP_COMMON_LIB_NATIVE_DIR=${HADOOP_PREFIX}/lib/native 

export HADOOP_OPTS="-Djava.library.path=$HADOOP_PREFIX/lib"

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