namenode启动失败

来源:1-13 -HDFS格式化及启停

慕尼黑5219940

2018-10-05

[xingtb@hadoop001 sbin]$ ./start-dfs.sh
18/10/05 19:16:59 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform… using builtin-java classes where applicable
Starting namenodes on [hadoop001]
hadoop001: Warning: Permanently added ‘hadoop001,192.168.174.140’ (ECDSA) to the list of known hosts.
hadoop001: starting namenode, logging to /home/xingtb/app/hadoop-2.6.0-cdh5.7.0/logs/hadoop-xingtb-namenode-hadoop001.out
localhost: Warning: Permanently added ‘localhost’ (ECDSA) to the list of known hosts.
localhost: starting datanode, logging to /home/xingtb/app/hadoop-2.6.0-cdh5.7.0/logs/hadoop-xingtb-datanode-hadoop001.out
Starting secondary namenodes [0.0.0.0]
0.0.0.0: Warning: Permanently added ‘0.0.0.0’ (ECDSA) to the list of known hosts.
0.0.0.0: starting secondarynamenode, logging to /home/xingtb/app/hadoop-2.6.0-cdh5.7.0/logs/hadoop-xingtb-secondarynamenode-hadoop001.out
18/10/05 19:17:15 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform… using builtin-java classes where applicable
[xingtb@hadoop001 sbin]$ jps

[xingtb@hadoop001 sbin]$ jps
13203 Jps
12825 DataNode
13007 SecondaryNameNode
[xingtb@hadoop001 sbin]$

写回答

3回答

慕尼黑5219940

提问者

2018-10-05

找到原因了

1
0

慕勒8140236

2019-06-20

请问怎么解决的呢,我也遇到了一样的问题


0
0

慕尼黑5219940

提问者

2018-10-05

我看到我的namenode在root用户下了,但是我是以普通用户启动的啊,另外两个进程都是普通用户的,这是为什么

0
1
Michael_PK
你看下nn的日志信息,是不是又遇到service ID不统一了
2018-10-05
共1条回复

以慕课网日志分析为例 进入大数据Spark SQL的世界

快速转型大数据:Hadoop,Hive,SparkSQL步步为赢

1644 学习 · 1129 问题

查看课程