Skip to main content

update error

sehabhost
[root@servers ~]# yum -y update Loaded plugins: fastestmirror, universal-hooks Determining fastest mirrors epel/x86_64/metalink | 29 kB 00:00:00 * EA4: ip * cpanel-addons-production-feed: ip * cpanel-plugins: ip * epel: mirror.dogado.de EA4 | 2.9 kB 00:00:00 cpanel-addons-production-feed | 2.9 kB 00:00:00 cpanel-plugins | 2.9 kB 00:00:00 Mysql-connectors-community | 2.6 kB 00:00:00 Mysql-tools-community | 2.6 kB 00:00:00 Mysql57-community | 2.6 kB 00:00:00 If above article doesn't help to resolve this issue please use

Comments

4 comments

Date Votes
  • vacancy
    yum clean all yum makecache yum -y upgrade Can you try?
    0
  • sehabhost
    yum clean all yum makecache yum -y upgrade Can you try?

    [root@servers ~]# yum makecache Loaded plugins: fastestmirror, universal-hooks Loading mirror speeds from cached hostfile epel/x86_64/metalink | 29 kB 00:00:00 * EA4: ip * cpanel-addons-production-feed: ip * cpanel-plugins: ip * epel: ftp.plusline.net EA4 | 2.9 kB 00:00:00 cpanel-addons-production-feed | 2.9 kB 00:00:00 cpanel-plugins | 2.9 kB 00:00:00 Mysql-connectors-community | 2.6 kB 00:00:00 Mysql-tools-community | 2.6 kB 00:00:00 Mysql57-community | 2.6 kB 00:00:00 If above article doesn't help to resolve this issue please use My View - CentOS Bug Tracker. One of the configured repositories failed (CentOS-7 - Base), 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=base ... 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 base or subscription-manager repos --disable=base 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=base.skip_if_unavailable=true failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
    0
  • techAMIGO
    HI sehabhost It the repo with Mirror List as a quick solution please do the following 1) you can backup the full repo directory as a precaution cp -prvf /etc/yum.repos.d /etc/yum.repos.d_old
    2) then do the following command to replace the current repository URL to another mirror URLs sed -i "s/vault.centos.org/mirrors.vinters.com/g" /etc/yum.repos.d/CentOS-*
    Then you can perform yum update.
    0
  • sehabhost
    HI sehabhost It the repo with Mirror List as a quick solution please do the following 1) you can backup the full repo directory as a precaution cp -prvf /etc/yum.repos.d /etc/yum.repos.d_old
    2) then do the following command to replace the current repository URL to another mirror URLs sed -i "s/vault.centos.org/mirrors.vinters.com/g" /etc/yum.repos.d/CentOS-*
    Then you can perform yum update.

    hi it work now. thanks so much techAMIGO
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post