问Cloudera Manager无法安装 cloudera-manager-agent 包？

无法安装 cloudera-manager-agent 包。 查看
/tmp/scm_prepare_node.6Y74boyT
using SSH_CLIENT to get the SCM hostname: 192.168.137.111 53966 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
END (0)
/etc/redhat-release ==> CentOS 7
正在检测 Cloudera Manager Server...
BEGIN host -t PTR 192.168.137.111
CentOS Linux release 7.9.2009 (Core)
END (1)
Host 111.137.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
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.137.111 7182
/usr/bin/python
END (0)
BEGIN which wget
END (0)
BEGIN wget -qO- -T 1 -t 1 http://169.254.169.254/latest/meta-data/public-hostname && /bin/echo
/usr/bin/wget
END (4)
正在安装包存储库...
Checking http://192.168.137.111/cdh6_parcel//redhat7/yum/repodata/repomd.xml
Checking http://192.168.137.111/cdh6_parcel//repodata/repomd.xml
Using
installing repository file /tmp/scm_prepare_node.6Y74boyT/repos/rhel7/cloudera-manager.repo
repository file /tmp/scm_prepare_node.6Y74boyT/repos/rhel7/cloudera-manager.repo installed
installing rpm keys
BEGIN gpg --import /tmp/scm_prepare_node.6Y74boyT/customGPG
END (0)
gpg: 钥匙环‘/tmp/scm_prepare_node.6Y74boyT/gnupg.5d1sTsYpea/secring.gpg’已建立
gpg: 钥匙环‘/tmp/scm_prepare_node.6Y74boyT/gnupg.5d1sTsYpea/pubring.gpg’已建立
gpg: /tmp/scm_prepare_node.6Y74boyT/gnupg.5d1sTsYpea/trustdb.gpg：建立了信任度数据库
gpg: 密钥 02A818DD：公钥“Cloudera Apt Repository”已导入
gpg: 密钥 E8F86ACD：公钥“Yum Maintainer <webmaster@cloudera.com>”已导入
gpg: 密钥 B0B19C9F：公钥“Parameterized Build <security@cloudera.com>”已导入
gpg: 密钥 84415700：公钥“Cloudera <security@cloudera.com>”已导入
gpg: 密钥 36F57F35：公钥“Cloudera <security@cloudera.com>”已导入
gpg: 合计被处理的数量：5
gpg: 已导入：5 (RSA: 3)
BEGIN rpm --import /tmp/scm_prepare_node.6Y74boyT/F36A89E33CC1BD0F71079007327574EE02A818DD.pub
END (0)
BEGIN rpm --import /tmp/scm_prepare_node.6Y74boyT/5F14D39EF0681ACA6F044A43F90C0D8FE8F86ACD.pub
END (0)
BEGIN rpm --import /tmp/scm_prepare_node.6Y74boyT/9543951160C284C0E7CA254573985D43B0B19C9F.pub
END (0)
BEGIN rpm --import /tmp/scm_prepare_node.6Y74boyT/CECDB80C4E9004B0CFE852962279662784415700.pub
END (0)
BEGIN rpm --import /tmp/scm_prepare_node.6Y74boyT/DF2C4DD7629B1AC08A0966E00F65552736F57F35.pub
END (0)
正在刷新包元数据...
BEGIN yum --disablerepo=* --enablerepo=cloudera* clean all
已加载插件：fastestmirror, langpacks
正在清理软件源： 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
已加载插件：fastestmirror, langpacks
Determining fastest mirrors
 
 
One of the configured repositories failed (未知),
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
已加载插件：fastestmirror, langpacks
已安装的软件包
cloudera-manager-agent.x86_64 6.3.1-1466458.el7 installed
END (0)
BEGIN echo oracle-j2sdk1.8 cloudera-manager-agent cloudera-manager-daemons | grep cloudera-manager-agent
END (0)
oracle-j2sdk1.8 cloudera-manager-agent cloudera-manager-daemons
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