码迷,mamicode.com
首页 > 其他好文 > 详细

cloudera manager报错解决方案

时间:2020-12-01 11:54:53      阅读:1      评论:0      收藏:0      [点我收藏+]

标签:assign   mem   lag   warning   异常   jdbc   font   echo   kernel   

问题1

错误提示:
cloudera-scm-agent 已死,但 pid 文件仍存
解决办法:

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

 

问题2

错误提示:

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

解决办法:

###查看ip及hostname对应关系
python -c ‘import socket; print socket.getfqdn(), socket.gethostbyname(socket.getfqdn())‘
  • 1
  • 2

 

问题3

错误提示:
??Cloudera Manager 正在获取安装锁
解决办法:

rm -rf /tmp/scm_prepare_node.*
rm -rf  /tmp/.scm_prepare_node.lock     
  • 1
  • 2

 

问题4

错误提示:

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

解决办法:

[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
  • 1
  • 2

 

问题5

错误提示:
??CDH安装过程中显示该版本过高,不能显示
解决办法:
??将postgresql中的data目录,重新命名。

问题6

错误提示:
技术图片
解决办法:

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

 

问题7

技术图片
解决办法:
??主机名不能含有_

问题8


技术图片
解决办法:

[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
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6

问题9

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

解决办法:

[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
  • 1
  • 2

问题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"
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6

解决办法:

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

问题10

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

解决办法:

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

问题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
  • 1
  • 2

解决办法:

rm -rf /var/lib/cloudera-scm-agent/cm_guid
  • 1

问题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  
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13

解决办法:

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

问题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
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11

解决办法:

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

问题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".
  • 1
  • 2
  • 3

解决方法:

1、关闭·一切关于postgresql的进程
2、查看日志
rm -r /var/lib/cloudera-scm-server-db/data/postmaster.pid
  • 1
  • 2
  • 3

问题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
  •  

解决方案:

将etc目录下的cloudera的repo文件中要设置gpgcheck=0


问题一 (Hive元数据库编码异常)

问题描述:
技术图片
解决方案:

##设置hive数据库编码为latin1
mysql > alter database hive character set latin1;
  • 1
  • 2

 

问题二 (JDBC版本异常)

问题描述:
技术图片
解决方案:

JDBC Driver版本过低引起的异常,使用高版本的JDBC驱动
  • 1

 

cloudera manager安装hive各种坑解决方案

问题三 (Mysql数据库异常)

问题描述:

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”

解决方案:

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

cloudera manager报错解决方案

标签:assign   mem   lag   warning   异常   jdbc   font   echo   kernel   

原文地址:https://www.cnblogs.com/shan13936/p/14040083.html

(0)
(0)
   
举报
评论 一句话评论(0
登录后才能评论!
© 2014 mamicode.com 版权所有  联系我们:gaon5@hotmail.com
迷上了代码!