Cloudera Manager5安裝總結遇到問題及解決辦法

安裝過程中，由於網絡終端，導致下面問題：

問題1：安裝停止在獲取安裝鎖
/tmp/scm_prepare_node.tYlmPfrT 
using SSH_CLIENT to get the SCM hostname: 172.16.77.20 33950 22 
opening logging file descriptor 

正在啟動安裝腳本...正在獲取安裝鎖...BEGIN flock 4 

這段大概過了半個小時，關閉selinux ! disabled

問題2：不能選擇主機

安裝失敗了，重新不能選主機

 


圖1
解決方案，需要清理安裝失敗文件
卸載 Cloudera Manager 5.1.x.和 相關軟件【官網翻譯：高可用】






問題3：DNS反向解析PTR localhost：

描述：

DNS反向解析錯誤，不能正確解析Cloudera Manager Server主機名
日志：

Detecting Cloudera Manager Server...
Detecting Cloudera Manager Server...
BEGIN host -t PTR 192.168.1.198
198.1.168.192.in-addr.arpa domain name pointer localhost.
END (0)
using localhost as scm server hostname
BEGIN which python
/usr/bin/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();' localhost 7182
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 localhost:7182, giving up
waiting for rollback request

解決方案：

將連不上的機器 /usr/bin/host 文件刪掉,執行下面命令：

1. sudo mv /usr/bin/host /usr/bin/host.bak

復制代碼

說明：

不明白cloudera的初衷，這里已經得到 Cloudera Manager Server的ip了，卻還要把ip解析成主機名來連接

由於DNS反向解析沒有配置好，根據Cloudera Manager Server 的ip解析主機名卻得到了localhost，造成之后的連接錯誤

這里的解決方案是直接把/usr/bin/host刪掉，這樣Cloudera Manager就會直接使用 ip進行連接，就沒有錯了

參考：

問題 4 NTP:

問題描述： 

Bad Health --Clock Offset

The host's NTP service did not respond to a request for the clock offset.

解決：

配置NTP服務

步驟參考：

CentOS配置NTP Server:

http://www.hailiangchen.com/centos-ntp/

國內常用NTP服務器地址及IP

http://www.douban.com/note/171309770/

修改配置文件：
[root@work03 ~]# vim /etc/ntp.conf

# Use public servers from the pool.ntp.org project.

# Please consider joining the pool ( http://www.pool.ntp.org/join.html).

server s1a.time.edu.cn prefer

server s1b.time.edu.cn

server s1c.time.edu.cn

restrict 172.16.1.0 mask 255.255.255.0 nomodify   <===放行局域網來源

啟動ntp
#service ntpd restart    <===啟動ntp服務
客戶端同步時間(work02,work03）：
ntpdate work01
說明：NTP服務啟動需要大約五分鍾時間，服務啟動之前，若客戶端同步時間，則會出現錯誤“no server suitable for synchronization found”
定時同步時間：
在work02和 work03上配置crontab定時同步時間

crontab -e
00 12 * * * root /usr/sbin/ntpdate 192.168.56.121 >> /root/ntpdate.log 2>&1 
問題 2.2
描述：
     Clock Offset

• Ensure that the host's hostname is configured properly.

• Ensure that port 7182 is accessible on the Cloudera Manager Server (check firewall rules).

• Ensure that ports 9000 and 9001 are free on the host being added.

• Check agent logs in /var/log/cloudera-scm-agent/ on the host being added (some of the logs can be found in the installation details).

問題定位：

在對應host（work02、work03）上運行 'ntpdc -c loopinfo'
[root@work03 work]# ntpdc -c loopinfo
ntpdc: read: Connection refused

解決：

開啟ntp服務：
三台機器都開機啟動 ntp服務
chkconfig ntpd on

問題 5 heartbeat:

錯誤信息：

Installation failed. Failed to receive heartbeat from agent.

解決：關閉防火牆

問題 6 Unknow Health：

Unknow Health
重啟后：Request to theHost Monitor failed.
service --status-all| grep clo
機器上查看scm-agent狀態：cloudera-scm-agent dead but pid file exists
解決：重啟服務
service cloudera-scm-agent restart

service cloudera-scm-server restart

問題 7 canonial name hostname consistent：

Bad Health

The hostname and canonical name for this host are not consistent when checked from a Java process.

canonical name：

4092 Monitor-HostMonitor throttling_logger WARNING  (29 skipped) hostname work02 differs from the canonical name work02.xinzhitang.com

解決：修改hosts 使FQDN和 hostname相同

ps：雖然解決了但是不明白為什么主機名和主機別名要一樣

/etc/hosts

192.168.1.185 work01 work01

192.168.1.141 work02 work02

192.168.1.198 work03 work03

問題 8 Concerning Health：

Concerning Health Issue

--  Network Interface Speed --

描述：The host has 2 network interface(s) that appear to be operating at less than full speed. Warning threshold: any.

詳細：

This is a host health test that checks for network interfaces that appear to be operating at less than full speed.
A failure of this health test may indicate that network interface(s) may be configured incorrectly and may be causing performance problems. Use the ethtool command to check and configure the host's network interfaces to use the fastest available link speed and duplex mode.

解決：

本次測試修改了 Cloudera Manager 的配置，應該不算是真正的解決