Linux中出现archive.cloudera.com报错怎么办

这篇文章主要介绍“Linux中出现archive.cloudera.com报错怎么办”，在日常操作中，相信很多人在Linux中出现archive.cloudera.com报错怎么办问题上存在疑惑，小编查阅了各式资料，整理出简单好用的操作方法，希望对大家解答”Linux中出现archive.cloudera.com报错怎么办”的疑惑有所帮助！接下来，请跟着小编一起来学习吧！

成都创新互联服务项目包括佛山网站建设、佛山网站制作、佛山网页制作以及佛山网络营销策划等。多年来，我们专注于互联网行业，利用自身积累的技术优势、行业经验、深度合作伙伴关系等，向广大中小型企业、政府机构等提供互联网行业的解决方案，佛山网站推广取得了明显的社会效益与经济效益。目前，我们服务的客户以成都为中心已经辐射到佛山省份的部分城市，未来相信会继续扩大服务区域并继续获得客户的支持与信任！

一.错误

[root@hadoop002 ~]# wget -c http://archive.cloudera.com/cm5/cm/5/cloudera-manager-centos7-cm5.16.2_x86_64.tar.gz
--2019-07-23 16:59:08--  http://archive.cloudera.com/cm5/cm/5/cloudera-manager-centos7-cm5.16.2_x86_64.tar.gz
Resolving archive.cloudera.com... failed: Temporary failure in name resolution.
wget: unable to resolve host address “archive.cloudera.com”

二.修改网卡，添加DNS

[root@hadoop002 ~]# vi /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=static
IPADDR=172.31.236.240
NETMASK=255.255.240.0
#百度DNS服务器
DNS1=180.76.76.76
#阿里云DNS服务器
DNS2=223.5.5.5

三.重启网络生效  切记

[root@hadoop002 ~]# service network restart
Shutting down interface eth0:                              [  OK  ]
Shutting down loopback interface:                          [  OK  ]
Bringing up loopback interface:                            [  OK  ]
Bringing up interface eth0:  Determining if ip address 172.31.236.240 is already in use for device eth0...
RTNETLINK answers: File exists
                                                           [  OK  ]
[root@hadoop002 ~]# ping archive.cloudera.com
PING prod.cloudera.map.fastly.net (151.101.76.167) 56(84) bytes of data.
64 bytes from 151.101.76.167: icmp_seq=1 ttl=59 time=0.719 ms
64 bytes from 151.101.76.167: icmp_seq=2 ttl=59 time=0.754 ms
^Z
[3]+  Stopped                 ping archive.cloudera.com
[root@hadoop002 ~]#

四.下载

[root@hadoop002 ~]# wget -c http://archive.cloudera.com/cm5/cm/5/cloudera-manager-centos7-cm5.16.2_x86_64.tar.gz
--2019-07-23 17:00:29--  http://archive.cloudera.com/cm5/cm/5/cloudera-manager-centos7-cm5.16.2_x86_64.tar.gz
Resolving archive.cloudera.com... 151.101.76.167
Connecting to archive.cloudera.com|151.101.76.167|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 837950600 (799M) [binary/octet-stream]
Saving to: “cloudera-manager-centos7-cm5.16.2_x86_64.tar.gz”
100%[=============================================================================>] 837,950,600 12.3M/s   in 65s     
2019-07-23 17:01:34 (12.4 MB/s) - “cloudera-manager-centos7-cm5.16.2_x86_64.tar.gz” saved [837950600/837950600]
[root@hadoop002 ~]# wget -c https://archive.cloudera.com/cdh6/parcels/latest/CDH-5.16.2-1.cdh6.16.2.p0.8-el7.parcel
--2019-07-23 17:01:58--  https://archive.cloudera.com/cdh6/parcels/latest/CDH-5.16.2-1.cdh6.16.2.p0.8-el7.parcel
Resolving archive.cloudera.com... 151.101.76.167
Connecting to archive.cloudera.com|151.101.76.167|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2132782197 (2.0G) [binary/octet-stream]
Saving to: “CDH-5.16.2-1.cdh6.16.2.p0.8-el7.parcel”
100%[===========================================================================>] 2,132,782,197 12.8M/s   in 2m 46s  
2019-07-23 17:04:44 (12.3 MB/s) - “CDH-5.16.2-1.cdh6.16.2.p0.8-el7.parcel” saved [2132782197/2132782197]
[root@hadoop002 ~]# wget -c https://archive.cloudera.com/cdh6/parcels/latest/CDH-5.16.2-1.cdh6.16.2.p0.8-el7.parcel.sha1
--2019-07-23 17:04:56--  https://archive.cloudera.com/cdh6/parcels/latest/CDH-5.16.2-1.cdh6.16.2.p0.8-el7.parcel.sha1
Resolving archive.cloudera.com... 151.101.76.167
Connecting to archive.cloudera.com|151.101.76.167|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 41 [text/plain]
Saving to: “CDH-5.16.2-1.cdh6.16.2.p0.8-el7.parcel.sha1”
100%[=============================================================================>] 41          --.-K/s   in 0s      
2019-07-23 17:04:56 (3.57 MB/s) - “CDH-5.16.2-1.cdh6.16.2.p0.8-el7.parcel.sha1” saved [41/41]
[root@hadoop002 ~]# wget -c https://archive.cloudera.com/cdh6/parcels/latest/manifest.json
--2019-07-23 17:05:09--  https://archive.cloudera.com/cdh6/parcels/latest/manifest.json
Resolving archive.cloudera.com... 151.101.76.167
Connecting to archive.cloudera.com|151.101.76.167|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 66804 (65K) [application/json]
Saving to: “manifest.json”
100%[=============================================================================>] 66,804      --.-K/s   in 0.001s  
2019-07-23 17:05:09 (44.2 MB/s) - “manifest.json” saved [66804/66804]

到此，关于“Linux中出现archive.cloudera.com报错怎么办”的学习就结束了，希望能够解决大家的疑惑。理论与实践的搭配能更好的帮助大家学习，快去试试吧！若想继续学习更多相关知识，请继续关注创新互联网站，小编会继续努力为大家带来更多实用的文章！