Errno 4 Socket Error
Contents |
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org > Fedora 23/24 > errno socket error errno 11004 getaddrinfo failed Using Fedora Yum [Errno 4] Socket Error: timed out on every mirror errno socket error python FedoraForum Search User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts Search Using socket error errno 10054 Fedora General support for current versions. Ask questions about Fedora that do not belong in any other forum. Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads socket error errno 10053 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: timed out on every mirror I get this error [Errno 4] Socket Error: timed out at every mirror, foreign and domestic, every
Socket Error Errno 10061
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% |=========================| 69 kB 00:03 updates-re: ################################################## 172/172 Added 0 new packages, deleted 9 old in 0.37 seconds primary.xml.gz 100% |=========================| 354 kB 00:06 extras : ################################################## 1040/1040 Added 1040 new packages, deleted 0 old in 4.83 seconds primary.xml.gz 100% |=========================| 800 kB 00:22 http://fedora.secsup.org/core/4/x86_...rimary.xml.g
[Errno 4] Socket Error: timed out - More info Messages sorted by: [ date ] [ thread
Socket Error Errno 10060
] [ subject ] [ author ] On 06/29/2011 07:58 AM socket error errno 10049 ken wrote: > Trying to update a second CentOS box, I'm getting this error repeatedly: > > socket error errno 10048 [Errno 4] Socket Error: timed out > > I'm getting this on every mirror and have gone through the list of > mirrors more than a dozen times. > http://forums.fedoraforum.org/showthread.php?t=60333 > Oddly, the RPMs I'm trying to upgrade I upgraded just yesterday without > a problem on another machine on the same LAN with no problems > whatsoever. I can ping mirrors fine. > > There were a spate of these errors back in 2006. The fix for many was > to add this line to yum.conf: https://lists.centos.org/pipermail/centos/2011-June/113380.html > > timeout=300 > > So I did that on the machine where yum is having the problem, but the > same errors are returned. > > Anyone else seeing this? Anyone know what the problem is? So I tried using wget to download RPMs from a few mirrors. I was able to successfully one whose size is about 5.5M, but the others all stop downloading around 1M. Then I tried ftp... same deal. This might be the reason for the "socket error" in yum. I don't have quotas set on this machine. selinux is on, but it's been on for years... why should it start interfering now? I'm downloading into /tmp where security settings are standard (user_u:object_r:tmp_t). Any ideas? Previous message: [CentOS] yum update -> [Errno 4] Socket Error: timed out Next message: [CentOS] yum update -> [Errno 4] Socket Error: timed out - More info Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the CentOS mailing list
error repeatedly:[Errno 4] Socket Error: timed outI'm getting this on every mirror and have gone through the list ofmirrors http://grokbase.com/t/centos/centos/116x9zdvkz/yum-update-errno-4-socket-error-timed-out more than a dozen times.Oddly, the RPMs I'm trying to upgrade http://forums.vpslink.com/centos/2631-yum-errno-4-socket-error-timed-out.html 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 socket error 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 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 socket error errno 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 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 Ke
Operating Systems Fedora Ubuntu CentOS Debian Gentoo About VPSLink Our Blog Infrastructure Datacenter Pictures Terms and Conditions Service Level Acceptable Use Jobs at VPSLink Contact Us Support Policies VPSLink Community Forums Wiki My.VPSLink.com Login Contact Us Full Root Access for a Fraction of a Dedicated Server's Cost CentOS Virtual Private Server Hosting at VPSLink will save you money over a dedicated server without sacrificing any administrative control. Whether you are scaling up from a shared hosting environment or looking to cut dedicated server costs, consider a CentOS VPS. VPSlink Forums > Operating Systems > CentOS YUM: [Errno 4] Socket Error: timed out User Name Remember Me? Password Register FAQ Community Calendar Today's Posts Search Community Links Social Groups Pictures & Albums Members List Search Forums Show Threads Show Posts Tag Search Advanced Search Google Site Search Go to Page... Thread Tools Display Modes #1 (permalink) 02-19-2008, 03:25 PM HelloVPS Junior Member Join Date: Feb 2008 Posts: 5 YUM: [Errno 4] Socket Error: timed out Hello, Does anyone know why I keep getting "[Errno 4] Socket Error: timed out Trying other mirror." why I try to use yum go install httpd, php, and etc? #2 (permalink) 02-19-2008, 08:14 PM DanL@VPSLink Administrator Join Date: Dec 2007 Posts: 1,141 1) Check your yum configuration to find the host(s) which yum is attempting to access 2) Use ping or dig to determine whether your VPS can resolve the yum repository's hostname to an IP (If you are unable to resolve the hostname, check your /etc/resolv.conf file to ensure working nameservers are specificed) 3) If working nameservers have been specified, check your firewall configuration to ensure you have not blocked incoming/outgoing DNS/HTTP connections Also, you may want to review this yum FAQ for further information (the link should have been provided as part of the yum error which you referenced). #3 (permalink) 02-19-2008, 09:46 PM HelloVPS Junior Member Join Date: Feb 2008 Posts: 5 From /etc/resolv.conf is the default from vpslink's fresh installation. I think it has to do with the sources in the repos. Do you recommend a good source for centos 5? #4 (permalink) 02-19-2