LinuxQuestions.org - yum ain't yummy...

- Fedora (https://www.linuxquestions.org/questions/fedora-35/)

- - yum ain't yummy... (https://www.linuxquestions.org/questions/fedora-35/yum-aint-yummy-373766/)

yum ain't yummy...

Sorry about the heading :D

This is what I am getting:

Code:

[root@localhost /]# yum -y update

Setting up Update Process

Setting up repositories

updates-released          100% |=========================|  951 B    00:01

extras                    100% |=========================| 1.1 kB    00:01

base                      100% |=========================| 1.1 kB    00:00

Reading repository metadata in from local files

All cool, huh?

This is where the whole thing goes down:

Code:

primary.xml.gz            100% |=========================|    0 B    00:08

http://www.fedora.is/fedora/core/upd...rimary.xml.gz: [Errno 4] Socket Error: timed out

Trying other mirror.

And it goes on and on and on...

I have dial up so there is not much I can do...

The yum.conf file is this:

Code:



[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

Why can't I update using yum? is it because the mirrors are really busy?

Hi.

You could try increasing the timeout. Put 'timeout=60' somewhere in yum.conf to get a 60 second timeout. The default's 30 seconds.

Dave

Thanks for replying! Here is the new yum.conf with the added line... Before destroying the world of Linux with this change to be implemented with the aid of VI could you please let me know if it is OK?

Thanks!

Code:



[main]

cachedir=/var/cache/yum

debuglevel=2

logfile=/var/log/yum.log

pkgpolicy=newest

distroverpkg=redhat-release

tolerant=1

exactarch=1

timeout=60 <-- IS HERE OK?

retries=20

obsoletes=1

gpgcheck=1



# PUT YOUR REPOS HERE OR IN separate files named file.repo

# in /etc/yum.repos.d

Yeah, that should be fine.

seems to be working

yum is downloading the headers as I post... This is what has happened so far:

Code:



[root@localhost ~]# yum -y update

Setting up Update Process

Setting up repositories

updates-released          100% |=========================|  951 B    00:00

extras                    100% |=========================| 1.1 kB    00:00

base                      100% |=========================| 1.1 kB    00:00

Reading repository metadata in from local files

primary.xml.gz            100% |=========================| 341 kB    06:22

updates-re: ################################################## 981/981

Added 981 new packages, deleted 0 old in 21.98 seconds

primary.xml.gz            100% |=========================| 896 kB    16:51

extras    : ################################################## 2485/2485

Added 2485 new packages, deleted 0 old in 37.76 seconds

primary.xml.gz            100% |=========================| 824 kB    15:27

base      : ################################################## 2772/2772

Added 2772 new packages, deleted 0 old in 41.29 seconds

Resolving Dependencies

--> Populating transaction set with selected packages. Please wait.

And is now downloading a bunch of headers like this one:

Code:

---> Downloading header for nc to pack into transaction set.

nc-1.82-fc4.1.i386.rpm    100% |=========================| 5.6 kB    00:04

This is the first time I do this right...

I edited the file to have a timeout of 120 seconds instead of 60 because I really wanted to make this work... Hopefully, the first time is the only time when this is going to be time-consuming and the next times I perform the yum -y update it will take less time...

What if the connection goes down? Will everything start from the beginning?

:newbie:

Thanks!

If the connection goes down, it'll restart downloading the last RPM from the start, and any already downloaded will not be re-downloaded.

Whenever i do an install of FC4 and issue Yum update there's around 200MB of updates, of course this includes Open office, firefox/thunderbird and all sorts of other big files.

If you're on dialup i'd say be careful issuing that command, i would suggest only installing the very base packages you need from the CDs, updating them, then using yum to install anything else you will need, this ensures you d/l the latest version straight off the bat with minimal bandwidth usage.

Yes, it seems that now things are going my way... I am limited to bouts of 2 hours of internet connection because of my provider but I have managed to work around this by doing the following

yum check-update

to see which updates I need to install.

I then proceeded to yum -y update z* to update all those packages starting with z and then yum update x* (without the -y flag this time because I suspected these were going to be huge...) The timeout suggestion for the yum.conf file was a lifesaver...