[Yum] Yum times out: Socket error 4, and 256

[Lorin Pino]

Johnny Hughes wrote:

>On Sun, 2006-02-26 at 07:30 -0600, Lorin Pino wrote:
>  
>
>>I am fairly new to linux, and brand new to yum (switching from Suse to 
>>CentOS).  I have been reading tutorials, and centos forum discussions, 
>>but I can't get yum to work:
>>[root at localhost home]# yum check-update
>>Setting up repositories
>>dries                     100% |=========================|  951 B    00:00
>>dag                       100% |=========================| 1.1 kB    00:00
>>jpackage-fc               100% |=========================|  951 B    00:00
>>update                    100% |=========================|  951 B    00:00
>>jpackage-generic          100% |=========================|  951 B    00:00
>>base                      100% |=========================| 1.1 kB    00:00
>>jpackage-rhel             100% |=========================|  951 B    00:00
>>contrib                   100% |=========================|  951 B    00:00
>>centosplus                100% |=========================|  951 B    00:00
>>addons                    100% |=========================|  951 B    00:00
>>extras                    100% |=========================| 1.1 kB    00:00
>>Reading repository metadata in from local files
>>primary.xml.gz            100% |=========================| 160 kB    00:38
>>http://ftp.belnet.be/packages/dries.ulyssis.org/redhat/el4/en/i386/dries/RPMS/repodata/primary.xml.gz: 
>>[Errno 4] Socket Error: timed out
>>Trying other mirror.
>>Error: failure: repodata/primary.xml.gz from dries: [Errno 256] No more 
>>mirrors to try.
>>
>>I have the keys installed.  I have tried using the base urls in the 
>>centos-base.repos, but when the computer is "Reading repository metadata 
>>in from local files
>>primary.xml.gz" it times out after about 15 seconds.  There is constant 
>>progress on the status bar, but it only gets 20%, or so, before timing 
>>out, and delivering the errors.  I am assuming there is a problem with 
>>my settings, but I don't know what to do from here.  Any suggestions?
>>TIA
>>_______________________________________________
>>    
>>
>
>This error is that you can't connect to http://ftp.belnet.be/ for the
>dries repo.
>
>Either remark out this repo, or pick another dries repo mirror and add
>to your repo file for dries.
>
>http://dries.ulyssis.org/rpm/mirrors.html
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Yum mailing list
>Yum at lists.dulug.duke.edu
>https://lists.dulug.duke.edu/mailman/listinfo/yum
>  
>
I tried removing the dries repo, and then got the same error for dags. 
On trying a different mirror for dries, I got the error much faster.
[root at localhost lorin]# yum update yum
Setting up Update Process
Setting up repositories
http://wftp.tu-chemnitz.de/pub/linux/dag/dries/repodata/repomd.xml: 
[Errno 4] IOError: HTTP Error 404: Not Found
Trying other mirror.
Cannot open/read repomd.xml file for repository: dries
failure: repodata/repomd.xml from dries: [Errno 256] No more mirrors to try.
Error: failure: repodata/repomd.xml from dries: [Errno 256] No more 
mirrors to try.

I removed dags and dries, and nothing worked with the centos repos at 
all, so I put in dags without dries and got the same thing:
[root at localhost lorin]# yum update yum
Setting up Update Process
Setting up repositories
dag                       100% |=========================| 1.1 kB    00:00
Reading repository metadata in from local files
primary.xml.gz            100% |=========================| 176 kB    00:41
http://apt.sw.be/redhat/el4/en/i386/dag/repodata/primary.xml.gz: [Errno 
4] Socket Error: timed out
Trying other mirror.
Error: failure: repodata/primary.xml.gz from dag: [Errno 256] No more 
mirrors to try.

1) Can you put more than one mirror in the file and have it go from one 
to the next, if it times out on the first?
2) I am on dial-up service.  Is this too slow to download this xml.gz 
file before the program times out?
    If so, is there a way to extend the time limit?
I assume from the progress percentage when it times out that this file 
is a meg, or slightly more, so this will take a few minutes to get on my 
connection, but the download is happening right up to the point when it 
times out (about 15-20 seconds).  Then the program shuts down.
So, any more suggestions?