Failure when receiving data from the peer

maintest1991

• March 23, 2019 10:54

hi friends i get problem when execute following command : yum update -y Could not retrieve mirrorlist

• 

  cPanelLauren

  • March 26, 2019 18:33

  Hello @maintest1991 Can you provide the output of the following: cat /etc/yum.repos.d/EA4.repo
cat yum.conf
rpm -qa |grep release
cat /etc/resolv.conf
  

  0
• 

  maintest1991

  • March 27, 2019 04:59

  yes ofcourse .. [EA4] name=EA4 ( EasyApache 4 ) mirrorlist= enabled=1 cost=50 *************************** [main] exclude=bind-chroot courier* dovecot* exim* filesystem httpd* mod_ssl* mydns* nsd* p0f php* proftpd* pure-ftpd* spamassassin* squirrelmail* tolerant=1 errorlevel=1 cachedir=/var/cache/yum/$basearch/$releasever keepcache=0 debuglevel=2 logfile=/var/log/yum.log exactarch=1 obsoletes=1 gpgcheck=1 plugins=1 installonly_limit=5 bugtracker_url=My View - CentOS Bug Tracker distroverpkg=centos-release # This is the default, if you make this bigger yum won't see if the metadata # is newer on the remote and so you'll "gain" the bandwidth of not having to # download the new metadata and "pay" for it by yum not having correct # information. # It is esp. important, to have correct metadata, for distributions like # Fedora which don't keep old packages around. If you don't like this checking # interupting your command line usage, it's much better to have something # manually check the metadata once an hour (yum-updatesd will do this). # metadata_expire=90m # PUT YOUR REPOS HERE OR IN separate files named file.repo # in /etc/yum.repos.d ***************************** mysql57-community-release-el6-11.noarch centos-release-6-10.el6.centos.12.3.x86_64 ***************************** nameserver 4.2.2.4 nameserver 8.8.8.8 thanks

  0
• 

  cPanelLauren

  • March 27, 2019 16:00

  Hi @maintest1991

  • The EA4 repo looks standard
  • The yum.conf appears to have no customizations
  • The CentOS release package is present
  • You're using Verizon's open DNS in conjunction with Google's - the only suggestion I might have here is to change the first entry to use 8.8.4.4 instead of 4.2.2.4 and try this again.

  Do you have any firewall-related customizations that might limit traffic to your server?

  0
• 

  maintest1991

  • March 28, 2019 05:06

  Error Fixed . I guess it was a problem with the network. For the last time, I run the following commands and error fixed : yum clean headers yum clean packages yum clean metadata yum clean dbcache yum clean all yum -y update If yum update failed : # rm -f /var/lib/rpm/__db.* # rpm -vv "rebuilddb # yum update Thanks

  0

Please sign in to leave a comment.