cloudera manager报错解决方案
2024-05-15 19:26:06
问题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_heartbeatself.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 connectself.timeout)File "/usr/lib64/python2.6/socket.py", line 567, in create_connectionraise 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 MTransaction 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: NOKEYPublic key for cloudera-manager-daemons-5.11.0-1.cm5110.p0.101.el6.x86_64.rpm is not installed解决方案：
将etc目录下的cloudera的repo文件中要设置gpgcheck=0cloudera manager报错解决方案相关推荐
- 金蝶星空cloud安装报错解决方案
在安装金蝶cloud时,安装完成了,但在登陆时,出现如下报错 解决方案: 在数据管理中心 你是否创建了账套,如果没有,就创建一个 你是否关联了站点 假如你的提示是这样子的,无法关联站点, 请检查下 这 ...
- TFS 报错解决方案:tf400324
TFS 报错解决方案:tf400324 参考文章: (1)TFS 报错解决方案:tf400324 (2)https://www.cnblogs.com/xiaz/p/7443805.html 备忘一下 ...
- vue-cli打包构建时常见的报错解决方案
vue-cli打包构建时常见的报错解决方案 参考文章: (1)vue-cli打包构建时常见的报错解决方案 (2)https://www.cnblogs.com/bester-ace/articles/ ...
- kali linux 安装 Mysql Can‘t read from messagefile 报错解决方案
kali linux 安装 Mysql Can't read from messagefile 报错解决方案 参考文章: (1)kali linux 安装 Mysql Can't read from ...
- CentOS 6安装Oracle报错解决方案
CentOS 6安装Oracle报错解决方案 参考文章: (1)CentOS 6安装Oracle报错解决方案 (2)https://www.cnblogs.com/lonecloud/p/689568 ...
- IDEA配置maven报错解决方案
IDEA配置maven报错解决方案 参考文章: (1)IDEA配置maven报错解决方案 (2)https://www.cnblogs.com/7758521gorden/p/8778496.html ...
- yum安装出现Error: Package: glibc-headers-2.17-157.el7.x86_64 (centos7.3)类似报错解决方案
yum安装出现Error: Package: glibc-headers-2.17-157.el7.x86_64 (centos7.3)类似报错解决方案 参考文章: (1)yum安装出现Error: ...
- 项目pom.xml第一行报错解决方案
项目pom.xml第一行报错解决方案 参考文章: (1)项目pom.xml第一行报错解决方案 (2)https://www.cnblogs.com/wantfly/p/9307476.html 备忘一 ...
- Eclipse中创建SpringBoot项目流程，及报错解决方案
Eclipse中创建SpringBoot项目流程,及报错解决方案 参考文章: (1)Eclipse中创建SpringBoot项目流程,及报错解决方案 (2)https://www.cnblogs.co ...
最新文章
- html鼠标悬停出现新元素,CSS：我如何将鼠标悬停在一个元素上，并显示另一个元素？...
- eclipse折叠所有代码快捷键
- 清华大学计算机系保送,2018年北大、清华五大学科竞赛集训队保送生争夺战结果...
- android+5.0+小米手环,小米手环5和荣耀手环6哪个好-参数对比
- SAP 3D visual enterprise viewer 9.0 的下载方式
- mysql fetch next from_MySql 存储过程 动态sql
- 基于OpenCL的mean filter性能
- 关于left join 一些测试
- 通信系统是如何收发复数信号的：IQ 调制原理
- DeepMind论文三连发：如何在仿真环境中生成灵活行为
- obspy中文教程（六）
- 软件工程导论 实验二 数据库设计
- Object类型转换为int型
- HALCON联合C#检测表面缺陷——显示实时灰度值以及灰度值的用处
- 光学成像基础-荧光滤色片
- jQuery引起的用layer弹出层上传文件不能获取文件名的解决(thinkphp5)
- 帧中继环境中NBMA模式下OSPF的配置
- 学习笔记 | 数据库概述 DB、DBMS、DBS
- 水下超声波测距c语言程序,超声波测距51C程序
- 【视频理解】论文串讲