CentOS yum安装报错，网络故障

2021 年 12 月 24 日

516 次浏览

2102字数

# 引言

CentOS 使用yum安装软件时候，报错，如下。

```bash
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.

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 retrieve metalink for repository: epel/x86_64. Please verify its path and try again
```

# 解决方案

1. 这个报错可能是因为没有网络连接，ping 114.114.114.114 试一试，能不能ping的通
   
   + 检查网络电缆以及驱动程序
2. 也有可能是dns解析故障，ping zunmx.top 试一试，能不能ping的通
   
   + 修改dns解析
     ```bash
     vi /etc/resolv.conf
     # 添加 
     nameserver 114.114.114.114
     # 退出vi
     # 重启网卡
     service network restart
     ```
3. yum 源问题，考虑重新修改base源