cloudera manager报错解决方案

本文总结了Cloudera Manager及其组件在安装、配置和运行过程中遇到的各种常见问题及其解决方法,包括Cloudera SCM Agent故障、网络连接问题、安装锁冲突等。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

问题1

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

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


问题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())'


问题3

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

rm -rf /tmp/scm_prepare_node.*
rm -rf  /tmp/.scm_prepare_node.lock     


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


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


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

解决办法:

①、将root用户添加到mysql 组
[root@hadoop07 ~]# useradd -g root mysql   
②、修改root用户的密码
问题10
ProtocolError: <ProtocolError for 127.0.0.1/RPC2: 401 Unauthorized>

解决办法:

$> ps -ef | grep supervisord
$> kill -9 <processID>
$> /etc/init.d/cloudera-scm-agent restart
问题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
问题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  

解决办法:

[root@hadoop2 yum.repos.d]# yum --setopt=tsflags=noscripts remove cloudera-manager-agent.x86_64 0:5.13.1-1.cm5131.p0.2.el6
问题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

解决办法:

修改客户端 /etc/cloudera-scm-agent/config.ini配置文件中service_host 为cloudera_server地址或者主机名并开启server端口7182
如:server_host=172.16.1.249
问题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、关闭·一切关于postgresql的进程
2、查看日志
rm -r /var/lib/cloudera-scm-server-db/data/postmaster.pid
问题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

### Cloudera SCM Agent 启动时报错 Traceback 的解决方案 #### 错误分析 当遇到 `cloudera-scm-agent` 启动失败并抛出 `Traceback` 错误时,可能的原因有多种。常见的原因包括目录权限不足、端口冲突以及配置文件设置不正确。 #### 权限问题处理 如果错误提示涉及获取目录属性失败,则可能是由于目标路径不存在或当前用户无权访问这些路径造成的。应确认 `/xx/log/cloudera-scm-agent` 和其他指定的日志存储位置确实存在,并且具有适当的读写权限[^1]。 ```bash sudo mkdir -p /xx/log/cloudera-scm-agent sudo chown -R cloudera-scm:cloudera-scm /xx/log/ ``` #### 端口占用排查 对于因尝试创建套接字而引发的异常——即本地回环接口上的特定端口已被占用的情况,建议先通过命令查看是否有其他服务正在使用相同端口: ```bash netstat -tuln | grep 9001 lsof -i :9001 ``` 一旦发现冲突的服务实例,可以选择停止它或将 `cloudera-scm-agent` 配置中的监听端口更改为未被使用的数值[^2]。 #### 修改配置文件 针对某些情况下需要调整通信参数的情形,在编辑位于 `/etc/cloudera-scm-agent/` 下的 `config.ini` 文件时,请确保其中定义的服务主机地址和服务端开放的端口均指向正确的CM Server节点及其默认对外开放的工作端口(通常是7182),以此来建立有效的连接关系[^3]。 ```ini [General] service_host=your_cloudera_manager_ip_or_hostname port=7182 ``` #### 调整网络策略 考虑到防火墙规则或其他安全措施可能会阻止必要的流量传输,适当放宽对Cloudera Manager所依赖的一系列内部通讯所需端口的安全限制也是解决问题的关键之一。例如允许所有来自本机的数据包到达 CM Server 上运行的应用程序监听的所有端口[^4]。
评论 7
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值