yum infinite [Error: timed out] looping

[gman1]

the story:

I did a fedora core 4 upgrade(not fresh install) from fedora core 3....

When doing a Yum update - Yum gets caught in an infinite timeout loop.... When it gets to 'Reading repository metadata in from local files' it ALWAYS times out after it gets to 6% and tries again and again and again....

There were 3 files in my 'yum.repos.d' folder with the extension '.rpmnew' so I changed them.... I basically just got rid of the '.rpmnew' extension from them.... I am guessing it did this becasue it did not want to write over my existing files, since I was doing a fedora core 4 upgrade....

fedora.repo.rpmnew to fedora.repo
fedora-updates.repo.rpmnew to fedora-updates.repo
fedora-updates-testing.repo.rpmnew to fedora-updates-testing.repo

Here is the shell output:
----------
[root@localhost gary]# yum update
Setting up Update Process
Setting up repositories
livna 100% |=========================| 951 B 00:00
updates-released 100% |=========================| 951 B 00:00
base 100% |=========================| 1.1 kB 00:00
extras 100% |=========================| 951 B 00:00
Reading repository metadata in from local files
primary.xml.gz 100% |=========================| 56 kB 00:19
http://fedora.arcticnetwork.ca/4/i38...rimary.xml.gz: [Errno 4] Sock et Error: timed out
Trying other mirror.
primary.xml.gz 100% |=========================| 48 kB 00:19
http://fr2.rpmfind.net/linux/fedora/...rimary.xml.gz: [Err no 4] Socket Error: timed out
Trying other mirror.
primary.xml.gz 100% |=========================| 64 kB 00:22
http://less.cogeco.net/pub/fedora/li...rimary.xml.gz: [Errno 4] Socket Error: timed out
Trying other mirror.
(it goes on forever from here)
----------

Here is my yum.conf:
----------
[main]
cachedir=/var/cache/yum
debuglevel=2
logfile=/var/log/yum.log
pkgpolicy=newest
distroverpkg=redhat-release
tolerant=1
exactarch=1
retries=20
obsoletes=1
gpgcheck=1

# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d

###############
## Livna.org ##
###############

[livna]
name=Livna.org Fedora Compatible Packages
baseurl=http://rpm.livna.org/fedora/$releasever/$basearch/RPMS.lvn
http://livna.cat.pdx.edu/fedora/$releasever/$basearch/RPMS.lvn
gpgcheck=1
----------

Thanks in advance for your help!

[jcliburn]

I'm having the same problem using a clean install of FC4. Yum worked perfectly for me on FC3. Have you discovered a solution yet?

[gman1]

jcliburn,

I sorta got yum working a litte.... I changed EVERYTHING back to the default core 4 setting(yum.conf & .repo files).... Then to add LIVNA I typed:

rpm -Uvh http://rpm.livna.org/fedora/4/i386/R...2.4.noarch.rpm

this make a liva repo file in the yum.repos.d folder.... Last night I finally got it to start download like 60 updates.... It would keep timeing out though and swiching repos.... I got about 15 of them anyway.... Now today I can't get it to download the updates again....

There are serious problems with yum now, and I don't know why everyone isn't complaining???? Maybe the fact that I am using dial up has something to do with it? For the life of me it makes no sense why it keeps timing out? I believe the new version of yum must have a serious bug in it....

[jcliburn]

Originally Posted by gman1

There are serious problems with yum now, and I don't know why everyone isn't complaining???? Maybe the fact that I am using dial up has something to do with it? For the life of me it makes no sense why it keeps timing out? I believe the new version of yum must have a serious bug in it....

Thanks. I'm using Direcway for internet connectivity. I get about 600kbps down/80 kbps up. I never had a single problem with yum under FC3 on dialup or satellite. Something is definitely wrong with it now. If you find out anything more, post it here. I'll do the same.

[mattdm]

Put timeout=45 in /etc/yum.conf. If that doesn't work, increase the number until the problem goes away. (The default is 30.)

[gman1]

I just got a message back from 'yum' they told me to add 'timeout=300' ti yum.conf.... The default is 30.... This addition to yum.conf seams to work....