2 fascinatinggirl fascinatingGirl 于 2016.02.27 08:05 提问

【萌芽求助】start-dfs.sh

我的namenode和datanode启动正常,但执行start-dfs.sh命令时,出现错误,
每句中都报..Could not resolve hostname...!

连接方式是hostonly,hadoop2.6.0

 [root@h1 ~]# cat /etc/hostname
192.168.1.101
[root@h1 ~]# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.1.101 h1
192.168.1.102 h2
192.168.1.103 h3
192.168.1.104 h4
192.168.1.105 h5
192.168.1.106 h6
192.168.1.107 h7
[root@h1 ~]# cat /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=h1

这是我自己的模拟搭建,多多包涵~
待大神解答n(*≧▽≦*)n

 [root@h1 ~]# **start-dfs.sh**
16/02/27 14:15:46 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
Starting namenodes on [Java HotSpot(TM) Client VM warning: You have loaded library /usr/local/hadoop-2.6.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'.
h1 h2]
sed: -e expression #1, char 6: unknown option to `s'
HotSpot(TM): ssh: Could not resolve hostname HotSpot(TM): Temporary failure in name resolution
warning:: ssh: Could not resolve hostname warning:: Temporary failure in name resolution
VM: ssh: Could not resolve hostname VM: Temporary failure in name resolution
You: ssh: Could not resolve hostname You: Temporary failure in name resolution
Java: ssh: Could not resolve hostname Java: Temporary failure in name resolution
have: ssh: Could not resolve hostname have: Temporary failure in name resolution
loaded: ssh: Could not resolve hostname loaded: Temporary failure in name resolution
which: ssh: Could not resolve hostname which: Temporary failure in name resolution
might: ssh: Could not resolve hostname might: Temporary failure in name resolution
disabled: ssh: Could not resolve hostname disabled: Temporary failure in name resolution
stack: ssh: Could not resolve hostname stack: Temporary failure in name resolution
library: ssh: Could not resolve hostname library: Temporary failure in name resolution
guard.: ssh: Could not resolve hostname guard.: Temporary failure in name resolution
The: ssh: Could not resolve hostname The: Temporary failure in name resolution
have: ssh: Could not resolve hostname have: Temporary failure in name resolution
VM: ssh: Could not resolve hostname VM: Temporary failure in name resolution
Client: ssh: Could not resolve hostname Client: Temporary failure in name resolution
fix: ssh: Could not resolve hostname fix: Temporary failure in name resolution
to: ssh: Could not resolve hostname to: Temporary failure in name resolution
try: ssh: Could not resolve hostname try: Temporary failure in name resolution
will: ssh: Could not resolve hostname will: Temporary failure in name resolution
guard: ssh: Could not resolve hostname guard: Temporary failure in name resolution
now.: ssh: Could not resolve hostname now.: Temporary failure in name resolution
the: ssh: Could not resolve hostname the: Temporary failure in name resolution
recommended: ssh: Could not resolve hostname recommended: Temporary failure in name resolution
stack: ssh: Could not resolve hostname stack: Temporary failure in name resolution
that: ssh: Could not resolve hostname that: Temporary failure in name resolution
It's: ssh: Could not resolve hostname It's: Temporary failure in name resolution
highly: ssh: Could not resolve hostname highly: Temporary failure in name resolution
with: ssh: Could not resolve hostname with: Temporary failure in name resolution
the: ssh: Could not resolve hostname the: Temporary failure in name resolution
-c: Unknown cipher type 'cd'
fix: ssh: Could not resolve hostname fix: Temporary failure in name resolution
you: ssh: Could not resolve hostname you: Temporary failure in name resolution
'execstack: ssh: Could not resolve hostname 'execstack: Temporary failure in name resolution
library: ssh: Could not resolve hostname library: Temporary failure in name resolution
link: ssh: Could not resolve hostname link: Temporary failure in name resolution
<libfile>',: ssh: Could not resolve hostname <libfile>',: Temporary failure in name resolution
with: ssh: Could not resolve hostname with: Temporary failure in name resolution
it: ssh: Could not resolve hostname it: Temporary failure in name resolution
or: ssh: Could not resolve hostname or: Temporary failure in name resolution
'-z: ssh: Could not resolve hostname '-z: Temporary failure in name resolution
noexecstack'.: ssh: Could not resolve hostname noexecstack'.: Temporary failure in name resolution
**h1: starting namenode**, logging to /usr/local/hadoop-2.6.0/logs/hadoop-root-namenode-h1.out
**h2: starting namenode**, logging to /usr/local/hadoop-2.6.0/logs/hadoop-root-namenode-h2.out
**192.168.1.105: starting datanode,** logging to /usr/local/hadoop-2.6.0/logs/hadoop-root-datanode-h5.out
**192.168.1.107: starting datanode**, logging to /usr/local/hadoop-2.6.0/logs/hadoop-root-datanode-h7.out
**192.168.1.106: starting datanode**, logging to /usr/local/hadoop-2.6.0/logs/hadoop-root-datanode-h6.out
Starting secondary namenodes [Java HotSpot(TM) Client VM warning: You have loaded library /usr/local/hadoop-2.6.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'.]
sed: -e expression #1, char 6: unknown option to `s'
HotSpot(TM): ssh: Could not resolve hostname HotSpot(TM): Temporary failure in name resolution
warning:: ssh: Could not resolve hostname warning:: Temporary failure in name resolution
Client: ssh: Could not resolve hostname Client: Temporary failure in name resolution
Java: ssh: Could not resolve hostname Java: Temporary failure in name resolution
which: ssh: Could not resolve hostname which: Temporary failure in name resolution
VM: ssh: Could not resolve hostname VM: Temporary failure in name resolution
have: ssh: Could not resolve hostname have: Temporary failure in name resolution
You: ssh: Could not resolve hostname You: Temporary failure in name resolution
might: ssh: Could not resolve hostname might: Temporary failure in name resolution
library: ssh: Could not resolve hostname library: Temporary failure in name resolution
loaded: ssh: Could not resolve hostname loaded: Temporary failure in name resolution
stack: ssh: Could not resolve hostname stack: Temporary failure in name resolution
have: ssh: Could not resolve hostname have: Temporary failure in name resolution
disabled: ssh: Could not resolve hostname disabled: Temporary failure in name resolution
guard.: ssh: Could not resolve hostname guard.: Temporary failure in name resolution
VM: ssh: Could not resolve hostname VM: Temporary failure in name resolution
The: ssh: Could not resolve hostname The: Temporary failure in name resolution
will: ssh: Could not resolve hostname will: Temporary failure in name resolution
stack: ssh: Could not resolve hostname stack: Temporary failure in name resolution
fix: ssh: Could not resolve hostname fix: Temporary failure in name resolution
to: ssh: Could not resolve hostname to: Temporary failure in name resolution
try: ssh: Could not resolve hostname try: Temporary failure in name resolution
recommended: ssh: Could not resolve hostname recommended: Temporary failure in name resolution
now.: ssh: Could not resolve hostname now.: Temporary failure in name resolution
guard: ssh: Could not resolve hostname guard: Temporary failure in name resolution
It's: ssh: Could not resolve hostname It's: Temporary failure in name resolution
you: ssh: Could not resolve hostname you: Temporary failure in name resolution
that: ssh: Could not resolve hostname that: Temporary failure in name resolution
the: ssh: Could not resolve hostname the: Temporary failure in name resolution
library: ssh: Could not resolve hostname library: Temporary failure in name resolution
highly: ssh: Could not resolve hostname highly: Temporary failure in name resolution
-c: Unknown cipher type 'cd'
the: ssh: Could not resolve hostname the: Temporary failure in name resolution
with: ssh: Could not resolve hostname with: Temporary failure in name resolution
<libfile>',: ssh: Could not resolve hostname <libfile>',: Temporary failure in name resolution
fix: ssh: Could not resolve hostname fix: Temporary failure in name resolution
'execstack: ssh: Could not resolve hostname 'execstack: Temporary failure in name resolution
link: ssh: Could not resolve hostname link: Temporary failure in name resolution
or: ssh: Could not resolve hostname or: Temporary failure in name resolution
with: ssh: Could not resolve hostname with: Temporary failure in name resolution
'-z: ssh: Could not resolve hostname '-z: Temporary failure in name resolution
it: ssh: Could not resolve hostname it: Temporary failure in name resolution
noexecstack'.: ssh: Could not resolve hostname noexecstack'.: Temporary failure in name resolution
16/02/27 14:16:04 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable

1个回答

devmiao
devmiao   Ds   Rxr 2016.02.28 07:02
Csdn user default icon
上传中...
上传图片
插入图片
准确详细的回答,更有利于被提问者采纳,从而获得C币。复制、灌水、广告等回答会被删除,是时候展现真正的技术了!
其他相关推荐
把问题消灭于萌芽状态
把问题消灭于萌芽状态--不需要你有力挽狂澜,扶大厦于将傾的本领,更需要你有未雨绸缪,防患于未然的意识。不要在无力回天的时候爆料出你的程序有一个斗大的漏洞,这对于项目经理来说无疑是一个晴天霹雳。有位大师说过:人类最大的毛病是自大、懒惰、怕麻烦!是的,这是人类普遍的毛病,当然,也是软件开发者经常会犯的毛病。知道有一些问题,或者说一些隐患存在,而由于自己的懒惰和怕麻烦,不去发现,不去
马贼——选自《萌芽》王若虚
马贼                         —— 作者:王若虚   我是个大学生,一个负责任的大学生。 我可以负责任的告诉你,我所在的这个学校住着一万两千六百八十二个学生,而停在学校各个角落的自行车,则有一万五千五百多辆。 好,现在问题的关键就是,那多出来的两千九百多辆自行车该怎么办?   问题的答案是:有我。               
从萌芽到壮大—机器视觉行业的发展
如今,中国机器视觉行业的发展呈现一片繁荣景象,目前行业总产值已逾十亿关口, 相关行业产值更是数以倍增, 视觉技术已经成为工业自动化领域的核心技术之一.   中国机器视觉行业是伴随中国工业化进程的发展而发展起来的,在发展历程中,大致经历了三个阶段。萌芽、发展、逐渐走向成熟。   在上世纪90年代,中国企业主要通过代理业务对客户进行服务。中国开始出现跨专业的机器视觉人才,从了解图像的采集和传输过程...
执行start-dfs.sh后,datenode没有启动
查看日志如下:   2014-06-18 20:34:59,622 FATAL org.apache.hadoop.hdfs.server.datanode.DataNode: Initialization failed for block pool Block pool (Datanode Uuid unassigned) service to localhost/127.0.0.1:900
22岁的创业萌芽:别让青春再流血
创业,对年轻人来说是一种诱惑;对创业中的人来说是一种压力;对创业成功后的大牛来说是种回忆,而对于岑辉宇来说,可以算是五味杂陈,在2016年与朋友体验接单的快感后,对创业的想法越来越浓厚,当然,创业并非一件容易的事,走错一步都可以一夜之间改变一个人的生活环境,因此,创业仅仅只是笔者的一个萌芽阶段,更多原因只是不想让青春再流血。 为什么说是萌芽阶段?为什么要分享出来?很多创业大咖都是成功
HADOOP1.0.3的start-dfs.sh系列脚本分析
熟悉脚本的启动过程,也就熟悉了hadoop的执行过程。所以研究并学习hadoop的脚本启动过程是非常有意义的。 对shell命令不是太熟悉,学的比较辛苦,里面还有些地方不明白,或者有错误的地方,希望如果有错误,能有人帮我指出来,谢谢。 (1)start-dfs.sh脚本 1)说明 start-dfs.sh可以单独运行,也可以启动start-all.sh时启动dfs进程。 start-df
start-dfs.sh无法启动namenode(jps查看不到namenode)
1.当启动hadoop后,一般会通过jps命令查看hadoop的启动情况,本人hadoop菜鸟一枚,在启动后一直看不到namenode的启动。   2.一般发生这种情况,我觉得有必要在hadoop文件夹下的logs文件夹里查看日志: 3.一般会查看.log文件,查看后如果发现tmp文件夹里找不到namenode,说明启动hadoop时没有产生name文件。 4.
【Hadoop】执行start-dfs.sh出错
问题1:hadoop2.7.3部署警告: Unable to load native-hadoop library for your platform 该警告通过如下方法消除了: dream361@ubuntu:/usr/local/hadoop/sbin$ vim /usr/local/hadoop/etc/hadoop/hadoop-env.sh 修改HADOOP_OPTS: expor
Hadoop cdh4.2.1 安装笔记
环境准备
Hadoop-2.2.0启动./start-dfs.sh报错解决方法
原博文地址: http://shisiyou.blog.51cto.com/9864147/1608060  绝对真实可用 问题描述: 开启Hadoop-2.2.0时,出现如下信息: [root@hd-m1 /]# ./hadoop/hadoop-2.6.0/sbin/start-all.sh  This script is Deprecated. Instead use