Cloudera经理。无法检测到Cloudera Manager Server

问题描述

我有两台配备了 CentOS 6.5的PC

  client86-101.aihs.net 80.94。 86.101 
 
 client86-103.aihs.net 80.94.86.103 
  

<$在client86-101.aihs.net上安装c $ c> cloudera-manager-server 。我在检测Cloudera Manager Server时遇到了问题（集群安装的第三步。）

问题追踪：

  BEGIN主机-t PTR 80.94.86.101 
 101.86.94.80.in-addr.arpa域名指针client86-101.aihs.net。 
 END（0）
使用client86-101.aihs.net作为scm服务器主机名
 BEGIN其中python 
 END（0）
 BEGIN python -c'import socket ;进口系统; s = socket.socket（socket.AF_INET）; s.settimeout（5.0） s.connect（（sys.argv [1]，int（sys.argv [2]）））; s.close（）;'client86-101.aihs.net 7182 
 / usr / bin / python 
 Traceback（最近一次调用最后一次）：
文件< string>，line 1，在< module> 
文件< string>，第1行，连接
 socket.error：[Errno 111]连接被拒绝
 END（1）
无法联系client端的scm服务器86 -101.aihs.net:7182，放弃
等待回滚请求
  

我想问题出在这个域名（ lient86-101.aihs.net ， client86-103.aihs.net ） 。因为如果你检查这个域名的IP地址，它将得到80.94.86.165这两个名字。但我不知道如何解决这个问题？

如果您需要更多数据，请告诉我。

对不起我的英文。

问题...

• 检查您正在运行CentOS x86_64


• 检查真实IP每个节点（ifconfig）。如果IP不是预期的IP，请编辑/ etc / sysconfig / network-scripts / ifcfg-以设置预期的固定IP并重新启动网络服务（/etc/init.d/network restart）
  
• 检查群集的每个节点文件/ etc / sysconfig / network是您节点的真实主机名（一个应该是client86-101.aihs.net和另一个client86-103.aihs.net）
>

• 在群集的每个节点中检查文件/ etc / hosts以将正确的IP地址分配给正确的主机名。


• 检查iptables已关闭（/etc/init.d/iptables stop&& chkconfig iptables off）


• 启动（或重新启动）客户端86-101.aihs.net中的cloudera-scm-server服务（服务client86-101.aihs.net启动（或重新启动））
  
• 删除您创建的任何现有群集Cloudera Manager，左侧，集群名称旁边的按钮，删除）


• 您应该能够重新启动CDH的部署过程你的群集。不要忘记在定义集群时指定两个节点，默认情况下，Cloudera Manager不管理承载Cloudera Manager Server的节点作为Hadoop节点。

请注意，Cloudera Manager希望/ etc / hosts的这种定义有效：

127.0.0.1 localhost

80.94.86.101 client86-101.aihs.net client86-101

80.94.86.103 client86-103.aihs.net client86-103

，并且这两个节点的配置应该完全相同。

希望这有助于

I have two PC's with CentOS 6.5

client86-101.aihs.net 80.94.86.101

client86-103.aihs.net 80.94.86.103

cloudera-manager-server installed on client86-101.aihs.net. I have the problem on detecting Cloudera Manager Server(3rd step on cluster installation.)

Issue trace:

BEGIN host -t PTR 80.94.86.101
101.86.94.80.in-addr.arpa domain name pointer client86-101.aihs.net.
END (0)
using client86-101.aihs.net as scm server hostname
BEGIN which python
END (0)
BEGIN python -c 'import socket; import sys; s = socket.socket(socket.AF_INET); s.settimeout(5.0); s.connect((sys.argv[1], int(sys.argv[2]))); s.close();' client86-101.aihs.net 7182
/usr/bin/python
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "<string>", line 1, in connect
socket.error: [Errno 111] Connection refused
END (1)
could not contact scm server at client86-101.aihs.net:7182, giving up
waiting for rollback request

I think the problem is in this domain names(lient86-101.aihs.net, client86-103.aihs.net). Because if you check this domain names ip-address it will get 80.94.86.165 for both names. But I don't know how I can fix this problem?

If you need some more data, please tell me.

Sorry for my english.

解决方案

If both DNS gives you the same IP, I confirm you've got a problem...

• Check you're running a CentOS x86_64
• Check the real IP of each node (ifconfig). If the IP is not the expected one, edit /etc/sysconfig/network-scripts/ifcfg- to set the expected fixed IP and restart the network service (/etc/init.d/network restart)
• Check in each node of your cluster the file /etc/sysconfig/network the real hostname of your node (one should be client86-101.aihs.net and the other client86-103.aihs.net)
• Check in each node of your cluster the file /etc/hosts to assign the correct IP Address to the correct hostname.
• Check iptables is off (/etc/init.d/iptables stop && chkconfig iptables off)
• Start (or restart) the cloudera-scm-server service in client86-101.aihs.net (service client86-101.aihs.net start (or restart))
• Delete any existing cluster you made (main page of Cloudera Manager, on the left, the button on the right next to the cluster(s) name(s), delete)
• You should be able to start again the deployment process of CDH on your cluster. Don't forget to specify the two nodes when you're defining your cluster, Cloudera Manager doesn't manage the node hosting the Cloudera Manager Server by default as a Hadoop node.

Note that Cloudera Manager is expecting such a definition of /etc/hosts to work :

127.0.0.1 localhost
80.94.86.101 client86-101.aihs.net client86-101
80.94.86.103 client86-103.aihs.net client86-103

and this configuration should be exactly the same for both nodes.

Hope this helps

这篇关于Cloudera经理。无法检测到Cloudera Manager Server的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！