Topic: 7.0 -> 7.1 Update Failed -- Suggestions?

[wjhobbs]

I just attempted to update a remote 7.0 server with 'yum update'. There were 253 files to be downloaded as part of the process. It failed while trying to download number 243.

I thought I could restart the process by entering 'yum update' again but that had no effect.

Here is the relevant portion of the console log:

Code: [Select]

(241/253): make-3.80-6.EL 100% |=========================| 336 kB    00:10
(242/253): e-smith-base-4 100% |=========================| 370 kB    00:07
http://mirror.contribs.org/smeserver/releases/7/smeos/i386/CentOS/RPMS/e-smith-backup-1.14.0-7.el4.sme.noarch.rpm: [Errno 4] IOError: <urlopen error (104, 'Connection reset by peer')>
Trying other mirror.
Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in ?
    yummain.main(sys.argv[1:])
  File "/usr/share/yum-cli/yummain.py", line 175, in main
    base.doTransaction()
  File "/usr/share/yum-cli/cli.py", line 659, in doTransaction
    problems = self.downloadPkgs(downloadpkgs)
  File "__init__.py", line 609, in downloadPkgs
  File "repos.py", line 624, in get
  File "/usr/lib/python2.3/site-packages/urlgrabber/mirror.py", line 414, in urlgrab
    return self._mirror_try(func, url, kw)
  File "/usr/lib/python2.3/site-packages/urlgrabber/mirror.py", line 392, in _mirror_try
    mirrorchoice = self._get_mirror(gr)
  File "/usr/lib/python2.3/site-packages/urlgrabber/mirror.py", line 290, in _get_mirror
    return gr.mirrors[gr._next]
IndexError: list index out of range
================================================================
No new rpms were installed. No additional commands are required.
================================================================
[root@server2 ~]# yum update
==============================================================
WARNING: Additional commands may be required after running yum
==============================================================
Loading "fastestmirror" plugin
Loading "smeserver" plugin
Setting up Update Process
Setting up repositories
smeaddons                 100% |=========================|  951 B    00:00
smeos                     100% |=========================|  951 B    00:00
smeupdates                100% |=========================|  951 B    00:00
Loading mirror speeds from cached hostfile
Reading repository metadata in from local files
primary.xml.gz            100% |=========================| 229 kB    00:00
smeos     : ################################################## 481/481
Added 301 new packages, deleted 305 old in 4.29 seconds
primary.xml.gz            100% |=========================|  54 kB    00:00
smeupdates: ################################################## 90/90
Added 90 new packages, deleted 0 old in 1.44 seconds
No Packages marked for Update/Obsoletion
================================================================
No new rpms were installed. No additional commands are required.
================================================================

What suggestions can you offer for completing the update?

Thanks for your help.

John

[pfloor]

Step 1.  Wait a day or 2 for the mirrors to get synced up.  Only 2 of the 4 seem to be correct and it is causing all kinds of problems.

Step 2. Then try again.
# yum clean all
# yum update

I don't think there is much you can do untill the mirrors are fixed.

[william_syd]

Step 1.  Wait a day or 2 for the mirrors to get synced up.  Only 2 of the 4 seem to be correct and it is causing all kinds of problems.

Does that mean yum and the mirrorlist system has failed to do it's intended task ?

[pfloor]

Well I guess you could say that however:

The entire mirror structure tree was re-arranged and it caused about 8 GIG if data to be moved and/or re-synced.  The mirrors have had a real hard time keeping up with it.  As a matter of fact the Nluug mirror is totally wrong.

A usual syncing of the mirrors is anywhere from a few Meg to as large as 500 Meg and that usually doesn't cause any problems.  This update/re-arrangement is 20 times the data movement in one day.

Couple that with everyone trying to download the recent updates and only 1 out of 4 mirrors at first being in sync and nothing will make yum work, not even the mirrorlist option.

The mirrorlist option is only as good as the mirrors that it has to choose from and those mirrors MUST be in sync and correct in a short period of time.  4 mirrors is just not enough especially when only 1 or 2 are correct and the others are taking far too long to correct themselves.

It's kind of like trying to drve your car (full with your family) on 3 flat tires and you only have 1 spare.  You're not going to get very far until you get a couple of those tires fixed.

[Agerskov]

The entire mirror structure tree was re-arranged and it caused about 8 GIG if data to be moved and/or re-synced.  The mirrors have had a real hard time keeping up with it.  As a matter of fact the Nluug mirror is totally wrong.

...

The mirrorlist option is only as good as the mirrors that it has to choose from and those mirrors MUST be in sync and correct in a short period of time.  4 mirrors is just not enough especially when only 1 or 2 are correct and the others are taking far too long to correct themselves.

How can you determine that all (or just a specific) mirror are finished syncing?

How can you configure your SME 7.0 so it uses a specific mirror?

[wjhobbs]

Paul,

Thank you for your reassuring explanation.

I tried a straight 'yum update' today (no 'clean all') and it just downloaded the missing 11 rpms and proceeded with the update. No problems at all.

I then updated another server without any difficulty.

The issues with the mirrors seems to be resolved.

John

[pfloor]

How can you determine that all (or just a specific) mirror are finished syncing?

You really can't unless you have access to the "master" mirror (and only a few select devs have that access).

If a mirrors is out of sync, yum will determine that and try another until it has tried all that are in the mirrorlist.  If it can't find a mirror that is correct then yum will fail (as it did over the last couple of days for some users).

How can you configure your SME 7.0 so it uses a specific mirror?

This would defeat the purpose of the mirrorlist option.  yum will try all the mirrors and use the first one that is good.

yum also uses the fastest_mirror plugin and uses the closest/fastest mirror first.  If that one fails it moves to the next and so on.

Please don't disable these features, they were added to ease the load on the mirrors.  Unfortunatly the last update was HUGE and a lot of users tried to update all at once.  The mirrors probably toped out at times and refuse connections and it also appears that it may have hindered the mirroring process as well.  We just don't have enough mirrors to handle it.  We are looking for more mirrors so if you know of any please visit this bug and tell us:
http://bugs.contribs.org/show_bug.cgi?id=2088