Ubuntu Hadoop群集未启动

Ubuntu Hadoop群集未启动,ubuntu,hadoop,hdfs,Ubuntu,Hadoop,Hdfs,我只是设置了一个hadoop集群(namenode+一个datanode)。但是,当我尝试启动hdfs时,会出现以下错误: hadoop@namenode:/opt/hadoop-2.2.0$ start-dfs.sh 14/01/30 20:18:50 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where app

我只是设置了一个hadoop集群(namenode+一个datanode)。但是,当我尝试启动hdfs时,会出现以下错误:

hadoop@namenode:/opt/hadoop-2.2.0$ start-dfs.sh
14/01/30 20:18:50 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 /opt/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'.
namenode]
sed: -e expression #1, char 6: unknown option to `s'
VM: ssh: Could not resolve hostname VM: Name or service not known
have: ssh: Could not resolve hostname have: Name or service not known
You: ssh: Could not resolve hostname You: 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
loaded: ssh: Could not resolve hostname loaded: Name or service not known
have: ssh: Could not resolve hostname have: Name or service not known
HotSpot(TM): ssh: Could not resolve hostname HotSpot(TM): Name or service not known
which: ssh: Could not resolve hostname which: Name or service not known
might: ssh: Could not resolve hostname might: Name or service not known
library: ssh: Could not resolve hostname library: 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
The: ssh: Could not resolve hostname The: Name or service not known
VM: ssh: Could not resolve hostname VM: Name or service not known
will: ssh: Could not resolve hostname will: Name or service not known
-c: Unknown cipher type 'cd'
try: ssh: Could not resolve hostname try: Name or service not known
Java: ssh: Could not resolve hostname Java: 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
stack: ssh: Could not resolve hostname stack: Name or service not known
now.: ssh: Could not resolve hostname now.: 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
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
that: ssh: Could not resolve hostname that: 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
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
'execstack: ssh: Could not resolve hostname 'execstack: Name or service not known
<libfile>',: ssh: Could not resolve hostname <libfile>',: Name or service not known
link: ssh: Could not resolve hostname link: No address associated with hostname
noexecstack'.: ssh: Could not resolve hostname noexecstack'.: Name or service not known
it: ssh: Could not resolve hostname it: No address associated with hostname
with: ssh: Could not resolve hostname with: Name or service not known
'-z: ssh: Could not resolve hostname '-z: Name or service not known
or: ssh: Could not resolve hostname or: Name or service not known
to: ssh: connect to host to port 22: Connection refused
namenode: starting namenode, logging to /opt/hadoop-2.2.0/logs/hadoop-hadoop-namenode-namenode.out
hadoop@namenode:/opt/hadoop-2.2.0$start-dfs.sh
14/01/30 20:18:50警告util.NativeCodeLoader:无法为您的平台加载本机hadoop库。。。在适用的情况下使用内置java类
正在[Java HotSpot(TM)64位服务器VM上启动namenodes警告:您已加载library/opt/hadoop-2.2.0/lib/native/libhadoop.so.1.0.0,该库可能已禁用堆栈保护。VM将立即尝试修复堆栈保护。
强烈建议您使用“execstack-c”修复库,或使用“-z noexecstack”链接库。
名称节点]
sed:-e表达式#1,字符6:s的未知选项
VM:ssh:无法解析主机名VM:名称或服务未知
have:ssh:无法解析主机名have:Name或服务未知
You:ssh:无法解析主机名You:Name或服务未知
64位:ssh:无法解析主机名64位:名称或服务未知
服务器:ssh:无法解析主机名服务器:名称或服务未知
警告::ssh:无法解析主机名警告::名称或服务未知
已加载:ssh:无法解析主机名已加载:名称或服务未知
have:ssh:无法解析主机名have:Name或服务未知
热点(TM):ssh:无法解析主机名热点(TM):名称或服务未知
which:ssh:无法解析主机名which:Name或service未知
可能:ssh:无法解析主机名可能:名称或服务未知
库:ssh:无法解析主机名库:名称或服务未知
guard.:ssh:无法解析主机名guard.:名称或服务未知
堆栈:ssh:无法解析主机名堆栈:名称或服务未知
禁用:ssh:无法解析主机名禁用:名称或服务未知
:ssh:无法解析主机名:名称或服务未知
VM:ssh:无法解析主机名VM:名称或服务未知
will:ssh:无法解析主机名will:Name或服务未知
-c:未知的密码类型“cd”
try:ssh:无法解析主机名try:Name或服务未知
Java:ssh:无法解析主机名Java:Name或服务未知
修复程序:ssh:无法解析主机名修复程序:名称或服务未知
:ssh:无法解析主机名:名称或服务未知
堆栈:ssh:无法解析主机名堆栈:名称或服务未知
现在::ssh:现在无法解析主机名。:名称或服务未知
guard:ssh:无法解析主机名guard:名称或服务未知
建议:ssh:无法解析主机名建议:名称或服务未知
高度:ssh:无法解析主机名高度:名称或服务未知
它的:ssh:无法解析主机名它的:名称或服务未知
that:ssh:无法解析主机名that:Name或service未知
you:ssh:无法解析主机名you:Name或服务未知
:ssh:无法解析主机名:名称或服务未知
修复程序:ssh:无法解析主机名修复程序:名称或服务未知
库:ssh:无法解析主机名库:名称或服务未知
with:ssh:无法解析主机名with:Name或服务未知
'execstack:ssh:无法解析主机名'execstack:名称或服务未知
“,:ssh:无法解析主机名”,:名称或服务未知
link:ssh:无法解析主机名link:没有与主机名关联的地址
noexecstack'。:ssh:无法解析主机名noexecstack'。:名称或服务未知
it:ssh:无法解析主机名it:没有与主机名关联的地址
with:ssh:无法解析主机名with:Name或服务未知
'-z:ssh:无法解析主机名'-z:名称或服务未知
或:ssh:无法解析主机名或:名称或服务未知
到:ssh:连接到主机到端口22:连接被拒绝
namenode:启动namenode,登录到/opt/hadoop-2.2.0/logs/hadoop-hadoop-namenode-namenode.out

我做错了什么?

我刚刚发现这是ubuntu上典型的hadoop错误。此问题的解决方案可在此处找到:

能否显示您的
启动dfs.sh
版本?您如何从项目根目录执行此操作?甚至可能
知道哪个启动dfs.sh
可能很有用。我可以从任何我想要的地方调用start-dfs.sh,因为我做了一个导出路径=$PATH:$HADOOP\u HOME/sbin;)