Cloudera MANAGER5 Installation Summary encountered problems and solutions

During the installation process, due to network terminal, the following problems are caused:

Issue 1: Installation stops getting the installation lock
/tmp/scm_prepare_node.tylmpfrt
Using Ssh_client to get the SCM hostname:172.16.77.20 33950 22
Opening logging File descriptor

starting installation Script ... getting installation lock ... BEGIN Flock 4

This is about half an hour, so turn off SELinux! Disabled

Issue 2: Cannot select host

Failed to install, cannot select host again




Figure 1
solution, you need to clean up the installation failure file
Uninstall Cloudera Manager 5.1.x. and related Software "official website translation: High Availability"






Problem 3:dns reverse parsing ptr localhost:

Describe:

DNS reverse resolution Error, Cloudera Manager server hostname not parsed correctly
Log:

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):
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

Solution:

Delete the machine/usr/bin/host file that cannot be connected, execute the following command:

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

Copy Code

Description: do not understand the original intention of Cloudera, here has been Cloudera Manager server IP, but also to resolve the IP to host name to connect because the DNS reverse resolution is not configured, according to Cloudera Manager Server IP resolution hostname is localhost, resulting in a connection error here the solution is to delete the/usr/bin/host directly, so that Cloudera Manager will directly use the IP connection, there is no wrong reference:

Issue 4 NTP:

Problem Description:

Bad health

--clock Offset

The

host's NTP service did not respond to a request for the Clock OFFSE T.

Solution:

Configuring the NTP service

Step Reference:

CentOS config NTP Server:

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

Domestic commonly used NTP server address and IP

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

To modify a configuration file:
[Email protected] ~]# 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 <=== release Local area network source

Start NTP
#service ntpd Restart <=== start NTP service
Client synchronization Time (WORK02,WORK03):
Ntpdate work01
Description: An error "no server suitable for synchronization found" occurs when the NTP service starts for approximately five minutes before the service starts, if the client synchronizes time
Timing Sync Time:
Configuring Crontab Timing Sync time on work02 and work03

Crontab-e
* * * * root/usr/sbin/ntpdate 192.168.56.121 >>/root/ntpdate.log 2>&1
Question 2.2
Describe:
Clock Offset

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

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

• Ensure that ports 9000 and 9001 is 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 found in the Installatio N details).

Problem Locator:

Run ' ntpdc-c loopinfo ' on the corresponding host (work02, work03)
[Email protected] work]# ntpdc-c loopinfo
Ntpdc:read:Connection refused

Solve:

To turn on the NTP service:
Three machines are powered on and start NTP service
Chkconfig ntpd

on

Question 5 Heartbeat:

error message:

installation failed. Failed to receive heartbeat from agent.

Workaround: Turn off the firewall

Question 6 Unknow Health:

Unknow Health
After reboot: Request to Thehost Monitor failed.
Service--status-all| grep CLO
View scm-agent status on machine: Cloudera-scm-agent dead but PID file exists
FIX: Restart Service
Service cloudera-scm-agent restartservice cloudera-scm-server Restart

Issue 7 Canonial name hostname consistent:

Bad

healththe hostname and canonical name for this host is not consistent when checked from a Java process.canonica L name:4092 monitor-hostmonitor Throttling_logger WARNING (skipped) hostname work02 differs from the canonical name Wo Rk02.xinzhitang.com FIX: Modify hosts to make the FQDN and hostname the same PS: although resolved but do not understand why the hostname and host alias is the same/etc/hosts192.168.1.185 work01 work01192.168.1.141 work02 work02192.168.1.198 work03 work03

Question 8 concerning health:

Concerning health issue--Network Interface Speed--Description: The host has 2 Network Interface (s), appear to is operating at Less than. Warning Threshold:any. Details: This is a host health test, checks for network interfaces, appear to being operating at Les s than full speed.
A failure of this health test may indicate the network interface (s) may is configured incorrectly and may be causing perf Ormance problems. Use the Ethtool command to check and configure the host's network interfaces to use the fastest available link speed and D Uplex mode.
Resolution: This test modifies the configuration of the Cloudera Manager and should not be considered a real solution

Cloudera MANAGER5 Installation Summary encountered problems and solutions