通過CM界面添加主機(jī)，第四步出現(xiàn)下面提示：

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安裝的，為什么添加主機(jī)時不能使用Server上的parcel，而是連接官方repo？