CDH add some new recording equipment to solve the problems encountered

Error message: MainThread agent ERROR Heartbeating to localhost: 7182 failed.
Solution: Configure Agent CM
cm of server and agent installation package is the same package, boot time startup command as the server or agent; cm have a working directory, you need to
Let's create; create a user; modifying agent configuration, assign it a location server; that port 7182 is the port server and agent communication;
server_host name server is configured;
modify files /opt/cloudera-manager/cm-5.4 .3 / etc / cloudera-scm- agent / config.ini in the server_host (three machines)


Error message: ERROR Heartbeating to master: 7182 failed .
Misinterpretation: sending to the specified port 7180 master node heartbeat failure.
First start Agent, which will generate a uuid, path: /opt/cm-5.1.3/lib/cloudera-scm-agent/uuid, if uuid Agent on each machine are the same, there will be an error case .
Error Solution:
go to the directory: cd /opt/cm-5.15.1/lib/cloudera-scm-agent/
delete uuid: rm -rf uuid
restart the agent: /opt/cm-5.15.1/etc/init.d/cloudera -scm-agent restart


Error message: 8475 MainThread agent ERROR Heartbeating appear when loudemanager installed to 192.168.30.1:7182 failed Problem Solution
# PS the AUX | grep Super
root 18949 0.0 0.1 223 624 12996 Ss 11:16 0:00 /opt/cm-5.7.0? / the lib64 / CMF / Agent / Build / the env / bin / Python /opt/cm-5.7.0/lib64/cmf/agent/build/env/bin/supervisord
the root 23390 112656 972 0.0 0.0 PTS / S 0 + 0 11:37 : 00 grep --color = Auto Super
# kill 18 949
sudo Service Agent Cloudera-scm-STOP

Unable to retrieve remote parcel repository manifest
does not affect the

error message: a KeyError: 'the getpwnam (): name Not found: SCM-Cloudera'
the groupadd SCM-Cloudera
the useradd -g Cloudera Cloudera-SCM SCM-
chown-SCM Cloudera: Cloudera-SCM / var / log / cloudera-scm (user information is missing)

Guess you like

Origin www.cnblogs.com/yaohaitao/p/11668887.html