Errno 4 Socket Error Yum
Contents |
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) errno socket error errno 11004 getaddrinfo failed Official Spins FedoraForum.org > Fedora 23/24 > Using Fedora Yum [Errno
Errno Socket Error Python
4] Socket Error: timed out on every mirror FedoraForum Search User Name Remember Me? Password Forgot
Socket Error Errno 10054
Password? Join Us! Register All Albums FAQ Today's Posts Search Using Fedora General support for current versions. Ask questions about Fedora that do not belong in any other forum.
Socket Error Errno 10053
Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 19th June 2005, 11:09 PM drunken_clam Offline Registered User Join Date: May 2005 Age: 44 Posts: 8 Yum [Errno 4] Socket Error: socket error errno 10061 timed out on every mirror I get this error [Errno 4] Socket Error: timed out at every mirror, foreign and domestic, every single time, trying to get primary.xml.gz. This has been going on for 3 days now. Every mirror will start to download it, some farther than others. I can download primary.xml..gz from each site directly. yum update or yum search Any ideas? Anything i can provide? Yum.log just displays what i've installed in the past, 4 packages from the first install when i was on my companies t1. Fedora4 dialup drunken_clam View Public Profile Find all posts by drunken_clam #2 21st June 2005, 03:03 AM jcliburn Offline Registered User Join Date: Nov 2004 Location: Mississippi, USA Posts: 1,180 I have the same problem. I haven't touched yum.conf. [root@osprey fc4]# yum install kernel-devel Setting up Install Process Setting up repositories updates-released 100% |=========================| 951 B 00:00 extras 100% |=========================| 951 B 00:00 base 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files primary.xml.gz 100%
Red Hat Certificate System Red Hat Satellite Subscription Asset Manager Red Hat Update Infrastructure Red Hat Insights Ansible Tower by Red Hat Cloud Computing Back Red Hat socket error errno 10060 CloudForms Red Hat OpenStack Platform Red Hat Cloud Infrastructure Red Hat Cloud socket error errno 10049 Suite Red Hat OpenShift Container Platform Red Hat OpenShift Online Red Hat OpenShift Dedicated Storage Back Red Hat Gluster socket error errno 10048 Storage Red Hat Ceph Storage JBoss Development and Management Back Red Hat JBoss Enterprise Application Platform Red Hat JBoss Data Grid Red Hat JBoss Web Server Red Hat JBoss Portal Red http://forums.fedoraforum.org/showthread.php?t=60333 Hat JBoss Operations Network Red Hat JBoss Developer Studio JBoss Integration and Automation Back Red Hat JBoss Data Virtualization Red Hat JBoss Fuse Red Hat JBoss A-MQ Red Hat JBoss BPM Suite Red Hat JBoss BRMS Mobile Back Red Hat Mobile Application Platform Services Back Consulting Technical Account Management Training & Certifications Red Hat Enterprise Linux Developer Program Support Get Support Production https://access.redhat.com/solutions/35848 Support Development Support Product Life Cycle & Update Policies Knowledge Search Documentation Knowledgebase Videos Discussions Ecosystem Browse Certified Solutions Overview Partner Resources Tools Back Red Hat Insights Learn More Red Hat Access Labs Explore Labs Configuration Deployment Troubleshooting Security Additional Tools Red Hat Access plug-ins Red Hat Satellite Certificate Tool Security Back Product Security Center Security Updates Security Advisories Red Hat CVE Database Security Labs Resources Overview Security Blog Security Measurement Severity Ratings Backporting Policies Product Signing (GPG) Keys Community Back Discussions Red Hat Enterprise Linux Red Hat Virtualization Red Hat Satellite Customer Portal Private Groups All Discussions Start a Discussion Blogs Customer Portal Red Hat Product Security Red Hat Access Labs Red Hat Insights All Blogs Events Customer Events Red Hat Summit Stories Red Hat Subscription Benefits You Asked. We Acted. Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences User Management Account Maintenance My Profile Notifications Help Log Out Language Back English español Deutsch italiano 한국어 français 日本語 português 中文 (中国) русский Customer Portal Search Products & Services Back Vie
error repeatedly:[Errno 4] Socket Error: timed outI'm getting this on every mirror and have gone through the list ofmirrors more than a dozen times.Oddly, the RPMs I'm trying to upgrade I upgraded just yesterday http://grokbase.com/t/centos/centos/116x9zdvkz/yum-update-errno-4-socket-error-timed-out withouta problem on another machine on the same LAN with no problemswhatsoever. I can ping mirrors fine.There were a spate of these errors back in 2006. The fix for many wasto add this line to yum.conf:timeout00So I did that on the machine where yum is having the problem, but thesame errors are returned.Anyone else seeing this? Anyone know what the problem is? reply Tweet Search Discussions Search All Groups centos 18 responses Oldest socket error Nested Giovanni Tirloni I would start by trying to telnet to port 80 on these mirrors, see if it can establish a connection, if not, who's blocking it, iptables, etc. -- Giovanni Tirloni -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.centos.org/pipermail/centos/attachments/20110629/a1bcda9e/attachment.html Giovanni Tirloni at Jun 29, 2011 at 2:06 pm ⇧ On Wed, Jun 29, 2011 at 8:58 AM, ken wrote:Trying to update a second CentOS box, I'm getting this socket error errno error repeatedly:[Errno 4] Socket Error: timed outI'm getting this on every mirror and have gone through the list ofmirrors more than a dozen times.Oddly, the RPMs I'm trying to upgrade I upgraded just yesterday withouta problem on another machine on the same LAN with no problemswhatsoever. I can ping mirrors fine.There were a spate of these errors back in 2006. The fix for many wasto add this line to yum.conf:timeout00So I did that on the machine where yum is having the problem, but thesame errors are returned.I would start by trying to telnet to port 80 on these mirrors, see if itcan establish a connection, if not, who's blocking it, iptables, etc.--Giovanni Tirloni-------------- next part --------------An HTML attachment was scrubbed...URL: http://lists.centos.org/pipermail/centos/attachments/20110629/a1bcda9e/attachment.html reply | permalink Ken Giovanni, Good thought. But that machine can reach port 80 on the mirrors... nothing blocking it. So it would appear that the problem is with yum itself... as installed on the problem machine. But it's been working fine for years and there's been no changes to yum.conf. I've upped the debug level (to 4). I'll run that awhile and see what I get. Thanks again. Ken at Jun 29, 2011 at 3:10 pm ⇧ On 06/29/2011 02:06 PM Giovanni Tirloni wrote:On Wed, Jun 29, 2011 at 8:58 AM, ken