问答博客标签用户活动
logo极客观点logo研发管理logoHarmonyOS
javascript
php
java
vue.js
git
html5
python
node.js
android
mysql
react.js
linux
ios
css
golang
spring
docker
程序员
logoONES 研发管理logo思否企业问答logo安谋科技 XPU

Cloudera Manager 添加主机无法安装 cloudera-manager-agent 包。

头像
wffger
    2031086110

    通过CM界面添加主机，第四步出现下面提示：

    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: [Errno 14] curl#35 - "TCP connection reset by peer" 
Trying other mirror. 


One of the configured repositories failed (Cloudera Manager, Version 5.14.1), 
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=cloudera-manager ... 

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

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=cloudera-manager.skip_if_unavailable=true 

failure: repodata/repomd.xml from cloudera-manager: [Errno 256] No more mirrors to try. 
https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.14.1/repodata/repomd.xml: [Errno 14] curl#35 - "TCP connection reset by peer" 
END (1) 
正在安装 cloudera-manager-agent 包...
BEGIN yum list installed cloudera-manager-agent 
Loaded plugins: fastestmirror 
Error: No matching Packages to list 
END (1) 
BEGIN yum info cloudera-manager-agent 
Loaded plugins: fastestmirror 
https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.14.1/repodata/repomd.xml: [Errno 14] curl#35 - "Network file descriptor is not connected" 
Trying other mirror. 


One of the configured repositories failed (Cloudera Manager, Version 5.14.1), 
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=cloudera-manager ... 

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

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=cloudera-manager.skip_if_unavailable=true 

failure: repodata/repomd.xml from cloudera-manager: [Errno 256] No more mirrors to try. 
https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5.14.1/repodata/repomd.xml: [Errno 14] curl#35 - "Network file descriptor is not connected" 
END (1) 
cloudera-manager-agent must have Version=5.14.1 and Build=1, exiting 
closing logging file descriptor

    CM Server 是通过本地parcel安装的，为什么添加主机时不能使用Server上的parcel，而是连接官方repo？

    cloudera
    阅读 16.5k
    4 个回答
    得票最新
    头像
    wffger
      2031086110
      ✓ 已被采纳
      头像
      sxx0317
        1
        新手上路，请多包涵

        我也碰到这个问题，求解

        头像
        不想错过就做
          1
          新手上路，请多包涵

          大佬，这个问题你解决啦没啊？我都2天没搞懂这个玩意

          头像
          midosun
            1
            新手上路，请多包涵

            我的安装也有这个问题，哪位能帮忙解释一下

            /tmp/scm_prepare_node.jBpCvLRu
            using SSH_CLIENT to get the SCM hostname: 192.168.1.100 56770 22
            opening logging file descriptor
            正在启动安装脚本...

            正在获取安装锁...

            BEGIN flock 4
            END (0)
            正在检测根权限...

            effective UID is 0
            正在检测分配...

            BEGIN grep Tikanga /etc/redhat-release
            END (1)
            BEGIN grep 'CentOS release 5' /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
            END (0)
            /etc/redhat-release ==> CentOS 7
            正在检测 Cloudera Manager Server...

            BEGIN host -t PTR 192.168.1.100
            CentOS Linux release 7.5.1804 (Core)
            END (127)
            /tmp/scm_prepare_node.jBpCvLRu/scm_prepare_node.sh: line 104: host: command not found
            BEGIN which 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();' 192.168.1.100 7182
            /usr/bin/python
            END (0)
            BEGIN which wget
            END (0)
            /usr/bin/wget
            BEGIN wget -qO- -T 1 -t 1 http://169.254.169.254/latest... && /bin/echo
            END (4)
            正在安装包存储库...

            validating format of repository file /tmp/scm_prepare_node.jBpCvLRu/repos/rhel7/cloudera-manager.repo
            installing repository file /tmp/scm_prepare_node.jBpCvLRu/repos/rhel7/cloudera-manager.repo
            repository file /tmp/scm_prepare_node.jBpCvLRu/repos/rhel7/cloudera-manager.repo installed
            正在刷新包元数据...

            BEGIN yum clean all
            Loaded plugins: fastestmirror, langpacks
            Cleaning repos: cloudera-manager iso
            Cleaning up everything
            Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos
            Cleaning up list of fastest mirrors
            END (0)
            BEGIN rm -Rf /var/cache/yum/x86_64
            END (0)
            BEGIN yum makecache
            Loaded plugins: fastestmirror, langpacks
            Determining fastest mirrors
            https://archive.cloudera.com/...: [Errno 14] curl#7 - "Failed connect to archive.cloudera.com:443; Connection refused"
            Trying other mirror.

            查看全部 4 个回答
            宣传栏