Yum [Errno 4] Socket Error: timed out on every mirror
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 15 of 15
  1. #1
    drunken_clam Guest

    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 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

  2. #2
    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.gz: [Errno 4] Socket Error: timed out
    Trying other mirror.
    primary.xml.gz 100% |=========================| 800 kB 00:26
    http://zeniv.linux.org.uk/pub/distri...rimary.xml.gz: [Errno 4] Socket Error: timed out
    Trying other mirror.
    http://ftp.ipv6.funet.fi/pub/mirrors...rimary.xml.gz: [Errno 4] IOError: <urlopen error (101, 'Network is unreachable')>
    Trying other mirror.
    primary.xml.gz 100% |=========================| 800 kB 00:31
    http://mirror.hiwaay.net/redhat/fedo...rimary.xml.gz: [Errno 4] Socket Error: timed out
    Trying other mirror.
    primary.xml.gz 100% |=========================| 800 kB 01:34
    http://ftp.isu.edu.tw/pub/Linux/Fedo...rimary.xml.gz: [Errno 4] Socket Error: timed out
    Trying other mirror.
    primary.xml.gz 100% |=========================| 72 kB 00:01


    Exiting on user cancel

    Does anyone have any ideas?

  3. #3
    drunken_clam Guest
    are you on dial up?

  4. #4
    Join Date
    Nov 2004
    Location
    Mississippi, USA
    Posts
    1,180
    Quote Originally Posted by drunken_clam
    are you on dial up?
    No, I'm on Direcway satellite. Yum worked fine on this connection using FC3, which I replaced with FC4 last evening.

  5. #5
    drunken_clam Guest
    Are you able to increase the debugging level at all? I tried briefly, last weekend with no luck.

  6. #6
    Join Date
    Nov 2004
    Location
    Mississippi, USA
    Posts
    1,180
    Quote Originally Posted by drunken_clam
    Are you able to increase the debugging level at all? I tried briefly, last weekend with no luck.
    I haven't tried. I'll try this evening when I get home.

  7. #7
    Join Date
    Jun 2004
    Posts
    92
    Add me to the list of people that have the same problem as you 2 guys.... Why doesn't everyone have the same problem as us? I am using dial up, and have tried everything under the sun, with not much luck....

  8. #8
    Join Date
    Nov 2004
    Location
    Mississippi, USA
    Posts
    1,180

    [Errno4] Socket error: SOLVED

    My ISP, Direcway, provides a web proxy on the satellite modem that I can't disable. In the past, apparently yum didn't care. With FC4, or yum 2.3.2, it apparently now does. I added the following line to /etc/yum.conf.

    proxy=http://192.168.0.1:87

    Yum is now working for me. No more socket error... Yay.

  9. #9
    Join Date
    Jun 2004
    Posts
    92
    jcliburn / drunken_clam,

    I sent a bug report to the email address located in 'man yum'(yum@lists.linux.duke.edu).... I will post any reply they give me here....

    Can you tell me more about this bug, maybe I too can figure out a way around it....

  10. #10
    Join Date
    Nov 2004
    Location
    Mississippi, USA
    Posts
    1,180
    Quote Originally Posted by gman1
    jcliburn / drunken_clam,

    I sent a bug report to the email address located in 'man yum'(yum@lists.linux.duke.edu).... I will post any reply they give me here....

    Can you tell me more about this bug, maybe I too can figure out a way around it....
    I noticed a regularity with which my errors occurred... No matter how many seconds elapsed during the transfer, the error always seemed to occur at or near the 800kB point. (See my post above to verify.) This set me to thinking about what could possibly be "filling up," as it were, and I thought about the Direcway satellite modem web proxy. I don't know if it has a cache (probably does), but on a lark I decided to look at the yum.conf manpage, where I found a "proxy" parameter. I added it to yum.conf and fiddled with it until I got the syntax right, then poof! It worked.

    Check to see if your ISP uses a web proxy. If it does, try adding it to yum.conf.

  11. #11
    Join Date
    Jun 2004
    Posts
    92
    I had a long conversation with my ISP, and the 'prozy' command is not a problem with my isp....

    HOWEVER I just got a message back from 'yum'.... They told me to add 'timeout=300' to my 'yum.conf' file.... The deault is set to 30(30 seconds that is).... This seams to work!!!!

  12. #12
    Ratt|ehead Guest
    I get similar errors - except mine is:
    [Errno 4] IOError: <urlopen error (97, 'Address family not supported by protocol')>
    Anyone know how to get around this?

  13. #13
    drunken_clam Guest
    thanks for the update, i'm going to try the timeout and verify i don't have a web proxy.
    either i'll try to post more information about the problem for gman1 or let everyone know what worked.

    thanks.

  14. #14
    drunken_clam Guest

    Thumbs up solution to my problem

    Quote Originally Posted by gman1
    I had a long conversation with my ISP, and the 'prozy' command is not a problem with my isp....

    HOWEVER I just got a message back from 'yum'.... They told me to add 'timeout=300' to my 'yum.conf' file.... The deault is set to 30(30 seconds that is).... This seams to work!!!!
    setting yum.conf to timeout=300 solved my problem, thanks.

  15. #15
    Join Date
    Dec 2012
    Location
    Eindhoven
    Posts
    1

    Re: Yum [Errno 4] Socket Error: timed out on every mirror

    All of this did not work with me.

    Using CentoS and yum.
    yum hangs without an error message, at least, so it appears...
    pressing ctrl-c does not work... (pressing it again and again and again does).

    Several things need to be checked...
    - are the repo's ok?
    - is networking ok?
    - are the yum & rpm databases ok?

    So, first start with the easy stuff... Clean the databases:
    rm -f /var/lib/rpm/__*
    rpm --rebuilddb -v -v
    yum clean all


    If that did not work...
    You can set a debug level, error level & timeout for yum at
    /etc/yum.conf

    debugelevel=1
    errorlevel=1
    timeout=1

    The timeout is standard 30 seconds. So if a repository (repo) does not respond, the error takes 30 seconds to appear...
    Als try using yum without the plugins (like fastest mirror & priorities) with the option --noplugins
    now starting yum again should give you faster and more info. Test with:

    yum --verbose --noplugins info

    You might get:

    Config time: 0.105
    Yum Version: 3.2.22
    Setting up Package Sacks
    Loading mirror speeds from cached hostfile
    * base: mirror.nl.leaseweb.net
    * extras: mirror.nl.leaseweb.net
    * ius: mirrors.ircam.fr
    * rpmforge: mirror.nl.leaseweb.net
    * updates: mirror.nl.leaseweb.net
    link-to-server-repository/repomd.xml: [Errno 4] IOError: <urlopen error (97, 'Address family not supported by protocol')>
    Trying other mirror.


    This indicates no information can be received from the server...
    try the url that is displayed by your yum (indicated above in red) in your web browser. Copy past it from your yum response! not from this post!
    If you get a list, you know the repository is on-line.

    If you get an error in your browser, try removing that repository from
    /etc/yum.repos.d

    Try to fetch the list on your server with wget and past the url

    wget link-to-server-repository/repomd.xml

    If this generates a Time-out, then there's a problem with your firewall or proxy settings.
    Try to disable your firewall.

    ConfigServer Security & Firewall
    If you are running csf & lfd you can disable csf with:
    csf -x

    try yum again and if it works, you'll have to reconfigure your csf.
    Enable csf again with
    csf -e

    And also check your proxy settings.
    You can also try to change the https in to http in the .repo files at
    /etc/yum.repos.d/

    Good luck!

Similar Threads

  1. connection timed out error
    By pcandpc in forum Servers & Networking
    Replies: 0
    Last Post: 22nd April 2008, 07:51 AM
  2. [Errno 4] Socket Error: timed out
    By maparus in forum Installation, Upgrades and Live Media
    Replies: 1
    Last Post: 31st July 2006, 01:54 AM
  3. YUM Error: [Errno -1] Header is not complete.
    By KimInWis in forum Using Fedora
    Replies: 11
    Last Post: 27th December 2005, 09:33 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •