質問1
エラー:
Clouderaの-SCM-Agentの死者が、PIDファイルが残っている
ソリューション:
[root@node1 ~]# cd /var/run/
[root@node1 run]# rm -rf cloudera-scm-agent.pid
質問2
エラーメッセージ:
エラー:いいえソケットは(「ノード1」、9000)上で作成することができなかった - [ERRNO 99]は要求されたアドレスを割り当てることができません。
ソリューション:
ホスト名、IP ###との対応関係を参照してください
パイソン-c '輸入ソケットを、印刷socket.getfqdn ()、socket.gethostbyname(socket.getfqdn())'
質問3
エラー:
ClouderaのManagerがロック設置取得
ソリューション:
RM -rf /tmp/scm_prepare_node.*
RM -rf /tmp/.scm_prepare_node.lock
質問4
エラーメッセージ:
エラー、CMサーバーのGUID、更新、期待b42773b1-6b8c-4536-84ae-975cef284c73、受信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は、名前を変更します。
質問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
エラー、CMサーバーのGUID、更新、期待b42773b1-6b8c-4536-84ae-975cef284c73、受信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の<127.0.0.1/RPC2用はProtocolError:401権限>
ソリューション:
$> ps -ef | grep supervisord
$> kill -9 <processID>
$> /etc/init.d/cloudera-scm-agent restart
質問11
[06/11月/ 2017年夜02時14分40秒0000] 22407 MainThreadエージェントERRORの
エラー、CMサーバのGUIDが更新され、85556d56-3e80-4811-be51-114000bb5ae9を予想、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
質問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
ソリューション:
Clouderaの設定したいetcディレクトリレポファイルgpgcheck = 0
問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)
ソリューション:
jdk1.7、置き換えjdk1.8、jarファイル互換性のない原因を使用します