CDH常见错误之主机添加

操作：添加主机节点

状态：安装失败。无法安装cloudera-manager-agent包

详细信息(错误)1：

/tmp/scm_prepare_node.4jhFYJdo
http://192.168.101.105/cdh6/6.3.1/parcels/allkeys.asc

server端日志信息：cloudera-scm-server.log

2023-03-24 14:19:36,938 ERROR CommandPusher:com.cloudera.cmf.command.flow.WorkOutputs: CMD id: 2677 Failed to complete installation on host node36.
2023-03-24 14:19:36,938 ERROR CommandPusher:com.cloudera.cmf.model.DbCommand: Command 2677(GlobalHostInstall) has completed. finalstate:FINISHED, success:false, msg:Failed to complete installation

处理：复制 allkeys.asc 到该 httpd 服务目录下，并授权 755，保证该 asc 文件能被访问到

http://192.168.101.105/cdh6/6.3.1/parcels/allkeys.asc

详细信息(错误)2：

/tmp/scm_prepare_node.4jhFYJdo
using SSH_CLIENT to get the SCM hostname: 192.168.101.105 58634 22
opening logging file descriptor
正在启动安装脚本...
正在获取安装锁...
BEGIN flock 4
END (0)
正在检测根权限...
effective UID is 0
正在检测分配...
BEGIN grep Tikanga /etc/redhat-release
END (1)
BEGIN grep 'Scientific Linux release 5' /etc/redhat-release
END (1)
BEGIN grep Santiago /etc/redhat-release
END (1)
BEGIN grep 'CentOS Linux release 6' /etc/redhat-release
END (1)
BEGIN grep 'CentOS release 6' /etc/redhat-release
END (1)
BEGIN grep 'Scientific Linux release 6' /etc/redhat-release
END (1)
BEGIN grep Maipo /etc/redhat-release
END (1)
BEGIN grep 'CentOS Linux release 7' /etc/redhat-release
CentOS Linux release 7.6.1810 (Core)
END (0)
/etc/redhat-release ==> CentOS 7
正在检测 Cloudera Manager Server...
BEGIN host -t PTR 192.168.101.105
;; connection timed out; no servers could be reached
END (1)
BEGIN which python
/usr/bin/python
END (0)
BEGIN python -c 'import socket; import sys; s = socket.socket(socket.AF_INET); s.settimeout(5.0); s.connect((sys.argv[1], int(sys.argv[2]))); s.close();' 10.194.186.40 7182
END (0)
BEGIN which wget
END (0)
/usr/bin/wget
BEGIN wget -qO- -T 1 -t 1 http://169.254.169.254/latest/meta-data/public-hostname && /bin/echo
END (4)
正在安装包存储库...
Checking http://192.168.101.105/cdh6/6.3.1/parcels//redhat7/yum/repodata/repomd.xml
Checking http://192.168.101.105/cdh6/6.3.1/parcels//repodata/repomd.xml
Using
installing repository file /tmp/scm_prepare_node.4jhFYJdo/repos/rhel7/cloudera-manager.repo
repository file /tmp/scm_prepare_node.4jhFYJdo/repos/rhel7/cloudera-manager.repo installed
installing rpm keys
BEGIN gpg --import /tmp/scm_prepare_node.4jhFYJdo/customGPG
gpg: keyring `/tmp/scm_prepare_node.4jhFYJdo/gnupg.oUEgcBoQmx/secring.gpg' created
gpg: keyring `/tmp/scm_prepare_node.4jhFYJdo/gnupg.oUEgcBoQmx/pubring.gpg' created
gpg: /tmp/scm_prepare_node.4jhFYJdo/gnupg.oUEgcBoQmx/trustdb.gpg: trustdb created
gpg: key 02A818DD: public key "Cloudera Apt Repository" imported
gpg: key E8F86ACD: public key "Yum Maintainer " imported
gpg: key B0B19C9F: public key "Parameterized Build " imported
gpg: key 84415700: public key "Cloudera " imported
gpg: key 36F57F35: public key "Cloudera " imported
gpg: Total number processed: 5
gpg: imported: 5 (RSA: 3)
END (0)
BEGIN rpm --import /tmp/scm_prepare_node.4jhFYJdo/F36A89E33CC1BD0F71079007327574EE02A818DD.pub
END (0)
BEGIN rpm --import /tmp/scm_prepare_node.4jhFYJdo/5F14D39EF0681ACA6F044A43F90C0D8FE8F86ACD.pub
END (0)
BEGIN rpm --import /tmp/scm_prepare_node.4jhFYJdo/9543951160C284C0E7CA254573985D43B0B19C9F.pub
END (0)
BEGIN rpm --import /tmp/scm_prepare_node.4jhFYJdo/CECDB80C4E9004B0CFE852962279662784415700.pub
END (0)
BEGIN rpm --import /tmp/scm_prepare_node.4jhFYJdo/DF2C4DD7629B1AC08A0966E00F65552736F57F35.pub
END (0)
正在刷新包元数据...
BEGIN yum --disablerepo=* --enablerepo=cloudera* clean all
Loaded plugins: fastestmirror, langpacks
Cleaning repos: cloudera-manager
Cleaning up list of fastest mirrors
END (0)
BEGIN rm -Rf /var/cache/yum/x86_64
END (0)
BEGIN yum --disablerepo=* --enablerepo=cloudera* makecache
Loaded plugins: fastestmirror, langpacks
Determining fastest mirrors


One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo= ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable 
or
subscription-manager repos --disable=

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=.skip_if_unavailable=true

Cannot find a valid baseurl for repo: cloudera-manager
END (1)
正在安装 cloudera-manager-agent 包...
BEGIN yum --disablerepo=* --enablerepo=cloudera* list installed cloudera-manager-agent
Loaded plugins: fastestmirror, langpacks
Installed Packages
cloudera-manager-agent.x86_64 6.3.1-1466458.el7 @cloudera-manager
END (0)
BEGIN echo oracle-j2sdk1.8 cloudera-manager-agent cloudera-manager-daemons | grep cloudera-manager-agent
oracle-j2sdk1.8 cloudera-manager-agent cloudera-manager-daemons
END (0)
BEGIN yum --disablerepo=* --enablerepo=cloudera* info cloudera-manager-agent
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile


One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo= ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable 
or
subscription-manager repos --disable=

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=.skip_if_unavailable=true

Cannot find a valid baseurl for repo: cloudera-manager
END (1)
cloudera-manager-agent must have Version=6.3.1 and Build=1466458, exiting
closing logging file descriptor

server端日志信息：cloudera-scm-server.log

2023-03-24 14:19:17,438 INFO NodeConfiguratorThread-12-0:com.cloudera.server.cmf.node.NodeConfiguratorProgress: node36: Transitioning from CHMOD (PT0.022S) to EXECUTE_SCRIPT
2023-03-24 14:19:17,441 INFO NodeConfiguratorThread-12-0:com.cloudera.enterprise.AbstractWrappedEntityManager: Rolling back transaction that wasn't marked for rollback-only.
java.lang.Exception: Non-thrown exception for stack trace.
        at com.cloudera.enterprise.AbstractWrappedEntityManager.close(AbstractWrappedEntityManager.java:161)
        at com.cloudera.cmf.persist.CmfEntityManager.close(CmfEntityManager.java:367)
        at com.cloudera.server.cmf.node.NodeConfigurator.getUserDefinedJavaHomebyHost(NodeConfigurator.java:921)
        at com.cloudera.server.cmf.node.NodeConfigurator.executeScript(NodeConfigurator.java:888)
        at com.cloudera.server.cmf.node.NodeConfigurator.configure(NodeConfigurator.java:1040)
        at com.cloudera.server.cmf.node.NodeConfigurator.run(NodeConfigurator.java:1106)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
2023-03-24 14:19:17,481 INFO NodeConfiguratorThread-12-0:com.cloudera.server.cmf.node.NodeConfigurator: Executing bash -c 'bash /tmp/scm_prepare_node.4jhFYJdo/scm_prepare_node.sh  --server_version 6.3.1 --server_build 1466458 --packages /tmp/scm_prepare_node.4jhFYJdo/packages.scm --always /tmp/scm_prepare_node.4jhFYJdo/always_install.scm --x86_64 /tmp/scm_prepare_node.4jhFYJdo/x86_64_packages.scm --certtar /tmp/scm_prepare_node.4jhFYJdo/cert.tar --unlimitedJCE false --javaInstallStrategy NONE --agentUserMode ROOT --cm http://192.168.101.105/cdh6/6.3.1/parcels/ --skipCloudConfig false | tee /tmp/scm_prepare_node.4jhFYJdo/scm_prepare_node.log; exit ${PIPESTATUS[0]}' on node36
2023-03-24 14:19:18,482 INFO NodeConfiguratorThread-12-0:com.cloudera.server.cmf.node.NodeConfiguratorProgress: node36: Transitioning from EXECUTE_SCRIPT (PT1.044S) to SCRIPT_START
2023-03-24 14:19:18,482 INFO NodeConfiguratorThread-12-0:com.cloudera.server.cmf.node.NodeConfiguratorProgress: node36: Transitioning from SCRIPT_START (PT0S) to TAKE_LOCK
2023-03-24 14:19:18,482 INFO NodeConfiguratorThread-12-0:com.cloudera.server.cmf.node.NodeConfiguratorProgress: node36: Transitioning from TAKE_LOCK (PT0S) to DETECT_ROOT
2023-03-24 14:19:18,482 INFO NodeConfiguratorThread-12-0:com.cloudera.server.cmf.node.NodeConfiguratorProgress: node36: Transitioning from DETECT_ROOT (PT0S) to DETECT_DISTRO
2023-03-24 14:19:18,482 INFO NodeConfiguratorThread-12-0:com.cloudera.server.cmf.node.NodeConfiguratorProgress: node36: Transitioning from DETECT_DISTRO (PT0S) to DETECT_SCM
2023-03-24 14:19:21,904 INFO scm-web-598262:com.cloudera.enterprise.JavaMelodyFacade: Entering HTTP Operation: Method:POST, Path:/add-hosts-wizard/installprogressdata.json
2023-03-24 14:19:21,906 INFO scm-web-598262:com.cloudera.enterprise.JavaMelodyFacade: Exiting HTTP Operation: Method:POST, Path:/add-hosts-wizard/installprogressdata.json, Status:200
2023-03-24 14:19:26,915 INFO scm-web-600152:com.cloudera.enterprise.JavaMelodyFacade: Entering HTTP Operation: Method:POST, Path:/add-hosts-wizard/installprogressdata.json
2023-03-24 14:19:26,917 INFO scm-web-600152:com.cloudera.enterprise.JavaMelodyFacade: Exiting HTTP Operation: Method:POST, Path:/add-hosts-wizard/installprogressdata.json, Status:200
2023-03-24 14:19:31,486 INFO NodeConfiguratorThread-12-0:com.cloudera.server.cmf.node.NodeConfiguratorProgress: node36: Transitioning from DETECT_SCM (PT13.004S) to REPO_INSTALL
2023-03-24 14:19:31,486 INFO NodeConfiguratorThread-12-0:com.cloudera.server.cmf.node.NodeConfiguratorProgress: node36: Transitioning from REPO_INSTALL (PT0S) to REFRESH_METADATA
2023-03-24 14:19:31,486 INFO NodeConfiguratorThread-12-0:com.cloudera.server.cmf.node.NodeConfiguratorProgress: node36: Transitioning from REFRESH_METADATA (PT0S) to PACKAGE_INSTALL cloudera-manager-agent
2023-03-24 14:19:31,925 INFO scm-web-599656:com.cloudera.enterprise.JavaMelodyFacade: Entering HTTP Operation: Method:POST, Path:/add-hosts-wizard/installprogressdata.json
2023-03-24 14:19:31,926 INFO scm-web-599656:com.cloudera.enterprise.JavaMelodyFacade: Exiting HTTP Operation: Method:POST, Path:/add-hosts-wizard/installprogressdata.json, Status:200
2023-03-24 14:19:31,948 WARN NodeConfiguratorThread-12-0:com.cloudera.server.cmf.node.NodeConfigurator: Command bash -c 'bash /tmp/scm_prepare_node.4jhFYJdo/scm_prepare_node.sh  --server_version 6.3.1 --server_build 1466458 --packages /tmp/scm_prepare_node.4jhFYJdo/packages.scm --always /tmp/scm_prepare_node.4jhFYJdo/always_install.scm --x86_64 /tmp/scm_prepare_node.4jhFYJdo/x86_64_packages.scm --certtar /tmp/scm_prepare_node.4jhFYJdo/cert.tar --unlimitedJCE false --javaInstallStrategy NONE --agentUserMode ROOT --cm http://192.168.101.105/cdh6/6.3.1/parcels/ --skipCloudConfig false | tee /tmp/scm_prepare_node.4jhFYJdo/scm_prepare_node.log; exit ${PIPESTATUS[0]}' on node36 finished with exit status 1
2023-03-24 14:19:31,949 INFO NodeConfiguratorThread-12-0:com.cloudera.server.cmf.node.NodeConfiguratorProgress: node36: Setting PACKAGE_INSTALL cloudera-manager-agent as failed and done state
2023-03-24 14:19:31,949 INFO NodeConfiguratorThread-12-0:net.schmizz.sshj.transport.TransportImpl: Disconnected - BY_APPLICATION
2023-03-24 14:19:33,137 INFO avro-servlet-hb-processor-7:com.cloudera.server.common.AgentAvroServlet: (39 skipped) AgentAvroServlet: heartbeat processing stats: average=13ms, min=6ms, max=35ms.
2023-03-24 14:19:33,137 INFO agentServer-587538:com.cloudera.server.common.MonitoringThreadPool: agentServer: execution stats: average=14ms, min=0ms, max=35ms.
2023-03-24 14:19:33,137 INFO agentServer-587538:com.cloudera.server.common.MonitoringThreadPool: agentServer: waiting in queue stats: average=0ms, min=0ms, max=1ms.
2023-03-24 14:19:36,935 INFO scm-web-598262:com.cloudera.enterprise.JavaMelodyFacade: Entering HTTP Operation: Method:POST, Path:/add-hosts-wizard/installprogressdata.json
2023-03-24 14:19:36,938 ERROR CommandPusher:com.cloudera.cmf.command.flow.WorkOutputs: CMD id: 2677 Failed to complete installation on host node36.
2023-03-24 14:19:36,938 ERROR CommandPusher:com.cloudera.cmf.model.DbCommand: Command 2677(GlobalHostInstall) has completed. finalstate:FINISHED, success:false, msg:Failed to complete installation

处理：该问题的错误结果并没有影响节点的添加，返回集群，并重新选择添加主机，选择 Add hosts to cluster 并继续，之后按提示在 install parcels 激活。

 检查主机正确性：针对感叹号部分进行处理

 为其创建 cloudera-scm 用户：

useradd --system  #表示创建的是系统用户
--home=/var/lib/cloudera-scm-server  #指定了用户的主目录
--no-create-home #表示不再创建用户的主目录
--shell=/bin/false  #不作为登陆用户 
--comment "Cloudera SCM User" 
cloudera-scm  #用户名

可参考博文进行搭建部署：CDH大数据平台入门篇之搭建与部署_啊 这的博客-CSDN博客

之后重新运行检查即可。。。