Hadoop learning problems encountered (CDH5.9.1 deployment issues encountered)

Question 1

Error: 
Cloudera-scm-Agent dead but pid files are still 
solutions:

[root@node1 ~]# cd /var/run/
[root@node1 run]# rm -rf cloudera-scm-agent.pid 

Question 2

Error message:

error: No socket could be created on (‘node1’, 9000) – [Errno 99] Cannot assign requested address

Solution:

See hostname ip ### and a correspondence relationship
python -c 'import socket; print socket.getfqdn (), socket.gethostbyname (socket.getfqdn ())'

Question 3

Error: 
  Cloudera Manager Getting lock installed 
Solution:

rm -rf /tmp/scm_prepare_node.*

rm -rf /tmp/.scm_prepare_node.lock

Question 4

Error message:

Error, CM server guid updated, expected b42773b1-6b8c-4536-84ae-975cef284c73, received 85556d56-3e80-4811-be51-114000bb5ae9

Solution:

[root@hadoop1 yum.repos.d]# rm -f /var/lib/cloudera-scm-agent/cm_guid 
[root@hadoop1 yum.repos.d]# /etc/init.d/cloudera-scm-agent restart

 

Question 5

Error: 
  displays the version is too high, CDH can not be displayed during installation 
Solution: 
  The postgresql in the data directory, rename. 

Question 6

Error message: 

 Solution:

[root@hadoop10 parcel-cache]# /etc/init.d/cloudera-  scm-agent restart
Stopping cloudera-scm-agent:                               [  OK  ]
Starting cloudera-scm-agent:                               [  OK  ]

Question 7

 Solution: 
  host name can not contain _ 

Question 8

Solution:

[root@hadoop2 cloudera-scm-agent]# sysctl -w vm.swappiness=10
[root@hadoop2 cloudera-scm-agent]# echo "vm.swappiness=10" >> /etc/sysctl.conf
[root@hadoop2 cloudera-scm-agent]# echo never > /sys/kernel/mm/transparent_hugepage/enabled   
[root@hadoop2 cloudera-scm-agent]# echo never > /sys/kernel/mm/transparent_hugepage/defrag 
[root@hadoop2 cloudera-scm-agent]# echo "echo never>/sys/kernel/mm/transparent_hugepage/defrag">> /etc/rc.local   
[root@hadoop2 cloudera-scm-agent]# echo "echo never>/sys/kernel/mm/transparent_hugepage/enabled">> /etc/rc.local

 

Question 9

Error, CM server guid updated, expected b42773b1-6b8c-4536-84ae-975cef284c73, received 85556d56-3e80-4811-be51-114000bb5ae9

Solution:

[root@hadoop1 yum.repos.d]# rm -f /var/lib/cloudera-scm-agent/cm_guid 
[root@hadoop1 yum.repos.d]# /etc/init.d/cloudera-scm-agent restart

Question 10

Starting Hive Metastore Server
javax.jdo.JDOFatalDataStoreException: Unable to open a test connection to the given database. JDBC url = jdbc:mysql://192.168.52.130:3306/hive_remote?createDatabaseIfNotExist=true, 
username = root. 
Terminating connection pool (set lazyInit to true if you expect to start your database after your app). 
Original Exception: ------
java.sql.SQLException: null,  message from server: "Host '192.168.52.128' is not allowed to connect to this MySQL server"

 

Solution:

①、将root用户添加到mysql 组
[root@hadoop07 ~]# useradd -g root mysql   
②、修改root用户的密码

Question 10

ProtocolError: <ProtocolError for 127.0.0.1/RPC2: 401 Unauthorized>

Solution:

$> ps -ef | grep supervisord
$> kill -9 <processID>
$> /etc/init.d/cloudera-scm-agent restart

Question 11

[06/Nov/2017 14:14:40 +0000] 22407 MainThread agent ERROR    
Error, CM server guid updated, expected 85556d56-3e80-4811-be51-114000bb5ae9, received b6eb96fc-4217-4ce1-b6c6-875ab84a7ba3
解决办法：

rm -rf /var/lib/cloudera-scm-agent/cm_guid
/opt/cloudera-manager/cm-5.9.1/lib/cloudera-scm-agent

Question 12

error reading information on service cloudera-scm-agent: No such file or directory
error: %preun(cloudera-manager-agent-5.13.1-1.cm5131.p0.2.el6.x86_64) scriptlet failed, exit status 1
Error in PREUN scriptlet in rpm package cloudera-manager-agent
Erasing    : cloudera-manager-daemons-5.13.1-1.cm5131.p0.2.el6.x86_64                                                          1/2 
cloudera-manager-agent-5.13.1-1.cm5131.p0.2.el6.x86_64 was supposed to be removed but is not!
  Verifying  : cloudera-manager-agent-5.13.1-1.cm5131.p0.2.el6.x86_64                                                            1/2 
  Verifying  : cloudera-manager-daemons-5.13.1-1.cm5131.p0.2.el6.x86_64                                                          2/2 

Removed:
  cloudera-manager-daemons.x86_64 0:5.13.1-1.cm5131.p0.2.el6                                                                         

Failed:
  cloudera-manager-agent.x86_64 0:5.13.1-1.cm5131.p0.2.el6  

Solution:

[root@hadoop2 yum.repos.d]# yum --setopt=tsflags=noscripts remove cloudera-manager-agent.x86_64 0:5.13.1-1.cm5131.p0.2.el6

 

Question 13

[30/Jan/2018 20:51:18 +0000] 9958 MainThread agent        ERROR    Heartbeating to localhost:7182 failed.
Traceback (most recent call last):
  File "/usr/lib64/cmf/agent/build/env/lib/python2.6/site-packages/cmf-5.13.1-py2.6.egg/cmf/agent.py", line 1412, in _send_heartbeat
    self.master_port)
  File "/usr/lib64/cmf/agent/build/env/lib/python2.6/site-packages/avro-1.6.3-py2.6.egg/avro/ipc.py", line 469, in __init__
    self.conn.connect()
  File "/usr/lib64/python2.6/httplib.py", line 771, in connect
    self.timeout)
  File "/usr/lib64/python2.6/socket.py", line 567, in create_connection
    raise error, msg
error: [Errno 111] Connection refused

Solution:

修改客户端 /etc/cloudera-scm-agent/config.ini配置文件中service_host 为cloudera_server地址或者主机名并开启server端口7182
如：server_host=172.16.1.249

Question 14

postgresql启动不起来，首先查看scm的日志，然后看db.log 
FATAL: pre-existing shared memory block (key 7432001, ID 0) is still in use
HINT:  If you're sure there are no old server processes still running, remove the shared memory block or just delete the file "postmaster.pid".

Solution:

1, all closed-course on the postgresql

2, view the logs rm -r /var/lib/cloudera-scm-server-db/data/postmaster.pid

Question 15

Dependencies Resolved

=====================================================================================================================================
 Package                              Arch               Version                                  Repository                    Size
=====================================================================================================================================
Installing:
 cloudera-manager-agent               x86_64             5.11.0-1.cm5110.p0.101.el6               cloudera-manager             9.1 M
Installing for dependencies:
 cloudera-manager-daemons             x86_64             5.11.0-1.cm5110.p0.101.el6               cloudera-manager             635 M

Transaction Summary
=====================================================================================================================================
Install       2 Package(s)

Total download size: 644 M
Installed size: 859 M
Downloading Packages:
(1/2): cloudera-manager-agent-5.11.0-1.cm5110.p0.101.el6.x86_64.rpm                                           | 9.1 MB     00:00     
(2/2): cloudera-manager-daemons-5.11.0-1.cm5110.p0.101.el6.x86_64.rpm                                         | 635 MB     00:15     
-------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                 42 MB/s | 644 MB     00:15     
warning: rpmts_HdrFromFdno: Header V4 DSA/SHA1 Signature, key ID e8f86acd: NOKEY

Public key for cloudera-manager-daemons-5.11.0-1.cm5110.p0.101.el6.x86_64.rpm is not installed

solution:

The cloudera the etc directory repo file you want to set gpgcheck = 0

 

Question 16

Caused by: com.fasterxml.jackson.databind.JsonMappingException: No content to map due to end-of-input
 at [Source: java.io.StringReader@458523c8; line: 1, column: 1]
	at com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:164)
	at com.fasterxml.jackson.databind.ObjectMapper._initForReading(ObjectMapper.java:2839)
	at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:2781)
	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:1942)

solution:

Use jdk1.7, replaced jdk1.8, jar incompatible cause