CDH常见错误之主机添加

已于 2023-03-24 15:43:36 修改
阅读量2k 收藏 2
点赞数 1
分类专栏： CDH 文章标签： linux 运维 大数据
于 2023-03-24 15:34:30 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_25868251/article/details/129750447
版权

操作：添加主机节点

状态：安装失败。无法安装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 <webmaster@cloudera.com>" imported
gpg: key B0B19C9F: public key "Parameterized Build <security@cloudera.com>" imported
gpg: key 84415700: public key "Cloudera <security@cloudera.com>" imported
gpg: key 36F57F35: public key "Cloudera <security@cloudera.com>" 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=<repoid> ...

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 <repoid>
or
subscription-manager repos --disable=<repoid>

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=<repoid>.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=<repoid> ...

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 <repoid>
or
subscription-manager repos --disable=<repoid>

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=<repoid>.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博客

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

啊 这
关注
  • 1
    点赞
  • 踩
  • 2
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
专栏目录
安装失败。 无法安装 cloudera-manager-agent 包。
weixin_42194239的博客
11-07 3771
File exists: ‘/var/log’ 进入var 目录，删除log文件
cdh 添加新主机
cyz52的博客
12-15 1435
1.1说明 CDH机器添加分三种方式 页面向导添加(最好离线) 软件包手动安装 原始码手动安装 第一种方式最简单，添加的节点会去主机下载安装包，但是在公网上ip反向解析域名，经常出错，离线会好点 第三种方式原始码安装需要自己指定管理目录 推荐第三种方式，会自动添加对应的服务，目录自动建立 这里分享第二种方式，软件包安装方法 1.2安装部署 主机名、ip等修改好，关闭防火墙，ssh免密码登录...
cdh6.2.1安装时账户免密登录验证失败问题解决
01-07
如题，在安装cdh6.2.1时，在验证agent主机的免密账号时，一直验证失败，打开日志显示 sudo tail -f /var/log/cloudera-scm-server/cloudera-scm-server.log ​ 2020-02-16 19:09:08,856 INFO NodeConfiguratorThread-10-0:com.cloudera.server.cmf.node.NodeConfiguratorProgress: hadoop08-test1-rgtj1-tj1: Setting AUTHENTICATE as failed and done state
无法安装 cloudera-manager-agent
前方的路在刚开始
07-19 1152
CDH6集群安装页面,Cannot find a valid baseurl for repo: cloudera-manager
无法安装 cloudera-manager-agent 包
poem_2010的博客
03-01 5487
支持 admin 升级 Cloudera Manager Agent 软件包 Install Agents 所有主机上的安装均失败。 已成功完成 1 个主机中的 0 个。 安装失败后已在 1 主机上卸载。 主机名称 IP 地址 进度 状态 poem1 192.168.22.136 重试 | 详细信息 安装失败。 已卸载。 × 无法安装 cloudera-manager-agent...
(5) cdh搭建 之 错误&解决
qiangweiyan的博客
03-13 9013
一、cloudera-scm-server 启动错误 1.1. Unable to retrieve non-local non-loopback IP address. 2019-07-01 17:55:00,197 ERROR ScmActive-0:com.cloudera.server.cmf.components.ScmActive: ScmActive: Unable to retri...
CDH-5.XX 离线安装及升级步骤及安装过程常见错误.txt
06-14
### CDH-5.XX离线安装与升级详解 #### 一、概述 随着大数据技术的发展，Apache Hadoop已经成为处理大规模数据集的核心...此外，熟悉安装过程中的常见错误及解决方法，有助于快速定位和解决问题，确保集群稳定运行。
CDH 离线部署文档.docx
06-10
- 配置 `/etc/hosts` 文件，添加各节点的 IP 地址和主机名映射。 3. **关闭 SELinux**： - 在 `/etc/sysconfig/selinux` 文件中将 `SELINUX` 设为 `disabled` 并重启系统。 4. **关闭防火墙**： - 临时关闭：`...
CDH详细安装教程
08-02
以下是对安装过程的详细步骤和常见问题的解答。 1. **硬件配置**：至少需要30GB的硬盘空间和一个CentOS（或Ubuntu）系统，建议使用英文版以避免后续数据传输问题。 2. **下载Cloudera Manager**：从官方地址...
CDH5搭建.pdf
06-12
- 完成安装后，可以使用Cloudera Manager Web UI来添加和配置其他节点。 2. **部署CDH包**: - 使用Cloudera Manager部署CDH包到各个节点。 - 配置HDFS、YARN等服务。 3. **配置服务**: - 根据实际需求配置HDFS...
cloudera-manager-agent-6.3.1-1466458.el7.x86_64.rpm
04-06
cloudera-manager-agent-6.3.1-1466458.el7.x86_64.rpm
CDH最新版本5.15.1下载
11-19
3. **配置环境变量**：编辑`.bashrc`或`.profile`文件，添加CDH的相关路径。 4. **启动服务**：运行`cloudera-scm-server`命令启动Cloudera Manager Server。 5. **创建集群**：在Cloudera Manager Web界面上，新建...
yum makecache出错，提示Cannot find a valid baseurl for repo:
枪枪枪的博客
08-29 930
[root@v102 ~]# yum clean all && yum makecache 已加载插件：fastestmirror 正在清理软件源： base cloudera-cdh cloudera-manager cloudera-repo epel extras updates Cleaning up list of fastest mirrors 已加载插件：fastestmirror Determining fastest mirrors One of the confi.
CDH安装
weixin_45465483的博客
10-14 314
安装包链接百度网盘：百度网盘 请输入提取码 提取码：fqf6 安装步骤 1、准备4台服务器 cdh1 cdh2 cdh3 cdh4 1、克隆base 1、修改主机名 vim /etc/sysconfig/network 通过 service network restart 重启网络服务生效 2、删除网卡配置 rm -rf /etc/udev/rules....
记一次 cdh6 service Connection refused 异常处理
qq_40462200的博客
07-16 5184
cdh6 service启动遇到问题 ：提示主机unhealthy 打开日志显示的是 ............................ Caused by: java.net.ConnectException: Connection refused (Connection refused) ..................... msg:Role not started due to unhealthy host ............................... 所有
yum install时，报错：Cannot find a valid baseurl for repo:base
weixin_39564277的博客
04-11 967
yum install时，报错：Cannot find a valid baseurl for repo:base 原因是没有配置正确的yum源。 我安装的是Centos6系统，修改使用阿里的yum源，可以使用。 这里我把我的配置文件内容贴上来，如果是使用Centos6系统可以直接覆盖用我这个，其他版本的可能需要修改下版本号就可以，具体没有试过。 yum源配置文件位置：/etc/yum.repos.d，CentOS-Base.repo即为配置文件，我把我的内容贴上来： CentOS-Base.repo T
Linux系统yum安装报错Cannot find a valid baseurl for repo的解决方法
热门推荐
郝猿的博客
05-29 1万+
1、进入到/etc/repos.d目录 cd /etc/yum.repos.d 2、修改CentOS-Media.repo vi CentOS-Media.repo 只修改后面的这几行就行了 baseurl=file:///mnt/cdrom/ file:///media/cdrecorder/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5 3、禁用默认的yum 网络源，将yum 网络源
cm6.2搭建遇到“安装失败。 无法安装 cloudera-manager-agent 包”问题
Master
10-19 4331
具体内容： BEGIN yum makecache BDB2053 Freeing read locks for locker 0x15f: 9033/140443655198528 Loaded plugins: fastestmirror https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.14.1/repodata/repomd.xml...
CDH安装失败了，如何重新安装
simle168的博客
04-03 1012
1&gt; 删除Agent节点的UUID       # rm -rf /opt/cm-5.12.0/lib/cloudera-scm-agent/*2&gt;  清空主节点CM数据库      进入主节点的Mysql数据库，然后drop database cm;3&gt; 删除Agent节点namenode和datanode节点信息     # rm -rf  /dfs/nn/*     # r...
cdh添加元数据库postgresql
最新发布
03-10
您好，关于cdh添加元数据库postgresql的问题，我可以回答。首先，您需要在CDH管理界面中选择“添加服务”，然后选择“PostgreSQL”作为您的元数据库。接下来，您需要配置PostgreSQL的相关参数，包括主机名、端口号、用户名和密码等。最后，您需要启动PostgreSQL服务并测试连接是否成功。希望这些信息能够对您有所帮助。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

啊 这

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值