Red Hat Bugzilla – Bug 152423
yum update hangs after retrieval of repository files
Last modified: 2014-01-21 17:51:39 EST
Description of problem:
After an upgrade FROM FC3 TO FC4T1, yum upgrade fails to continue after retrieval of repository xml
Version-Release number of selected component (if applicable):
Tried with the vanilla yum version from fc4t1 and even with the newer version in development. Both
versions hang after grabbing the repository data.
Do an upgrade from FC3 to FC4T1, reboot the machine once install has completed. Run yum check-
update and see that there are several packages to be updated from development repo. Run yum -y
update and watch the repository data files be retrieved and it will sit and hang for hours until you issue
Steps to Reproduce:
1. Do an upgrade from FC3 to FC4T1, reboot the machine once install has completed.
2. Run yum check-update and see that there are several packages to be updated from development
3. Run yum -y update and watch the repository data files be retrieved and it will sit and hang for hours
until you issue a SIGKILL.
Same as described above
Yum to update the necessary packages to bring the install up to the level of development repository for
can you attach a 'yum -d 5 update' output?
This isn't a high severity problem. It's not happening all over.
thats part of the problem, NO I CANNOT, it hangs forever and no output to
console. Any suggestions? How about i blow away all the repository xml files and
re-try? Although i have done this already numerous times...something is
definitely afoot at the circle K. The issue is critical to me as i will be doing
this to over 600 servers to upgrade from rh73 to fcX - and if fc4 isnt useable
.... you get the drift
so you run:
yum -d5 update and you get NO OUTPUT AT ALL?
not even the outputting of the yum version, nada?
[root@b-52 ~]# yum -d5 update
Yum Version: 2.3.1
COMMAND: yum -d5 update
Setting up Update Process
Setting up Repos
Baseurl(s) for repo:
and then hung up, I've to ctrl-c to stop the process...
I forgot: My Fedora Core 4 was a clean install
i get absolutely NO OUTPUT whatsoever, it sits and hangs after reporting on the
development repository, and will hang until killed - doesnt appear to zombie
however, so this behavior is a little strange.
Comment number 5: try two things:
1. cd /var/lib/rpm ; rm __db*
2. rpm --rebuilddb
3. re run yum
comment number 7: run this:
python -c 'import yum; my=yum.YumBase()'
and tell me what it does.
Created attachment 112421 [details]
Yum update output
this is the output after waiting about 2 hours or so
Follow the instructions here:
and see if yum becomes much more responsive.
Also how much/little ram do you have?
Its a Sony Vaio PCG-F480 with 256M RAM and 512M Swap (i know i know, its rather slow, lol) Trying
the faq instruction now.
okid disabled ipv6 (not having ipv6 enabled and running makes me curious why we feel this would
improve yum's performance), rebooted, ran yum -d5 update (this is yum-2.3.1-3) and the output is as
Yum Version 2.3.1
COMMAND: yum -d5 update
Setting up Update Process
Setting up Repos
Baseurl(s) for repo:['http://download.fedora.redhat.com/pub/fedora/linux/core/development/
development 100% |======================| 1.1kB 00:00
Reading repository metadata in from local files
Setting up Package Sacks
Excluding Incomaptible Archs
Reading Local RPMDB
Building updates object
and there it hangs.....still
Btw the import of YumBase() works fine, no errors nor tracebacks come back.
(In reply to comment #8)
> Comment number 5: try two things:
> 1. cd /var/lib/rpm ; rm __db*
> 2. rpm --rebuilddb
> 3. re run yum
Same thing...this is after I have done the 3-steps and turned off ipv6.
I've an Athlon64 3000+ with 1 GB of ram.
I've also some other strange things: my network (nforce4's net on board, I've
a MSI K8N Platinum) works ok, however I cannot go to the internet, but see my
Is it related?
Thanx for help!
Created attachment 112435 [details]
Network is active...but some programs tell the opposite!
Well, not wanting to, but in an effor to help debug, i blew away the rpm db files and regenerated them,
and then tried to re-run yum (yum -y update). Interestingly enough, after running the --rebuilddb the
dbs were created then removed from the system. Bottom line is THAT SEEMED TO FIX THE ISSUE for me.
Waiting for it complete, to report the final results, but its further along than it was prior to the removal
and reconstruction of the rpm db.
Additional, unrelated question however, isnt it better to do a rpmdb --rebuild rather than rpm --
rebuilddb ? Or is one a wrapper around the other?
the yum -y update completed, transactions failed due to a slew of deps but it DID complete as
expected. Now to work through the tide of errors on deps, its a rather lenghty list, as illustrated in my
attacment # 112421 (617 packages flagged to be updated, with a bunch of deps) does that sound
you got dep errors? Are you sure they were dependencies? Yum doesn't allow an
unresolved transaction to execute.
We've seen that some systems with ipv6 enabled will stall out trying to resolve
the AAAA record of their repositories. It's happened repeatedly, mostly due to
Comment #16: pretty sure it's the same program just wrapped differently.
Comment #15: I think you've got some network problems to address first. Please
make sure you're able to contact all of your repositories and/or mirrorlists in
your yum .repo files via a web browser first.
(In reply to comment #18)
> Comment #15: I think you've got some network problems to address first. Please
> make sure you're able to contact all of your repositories and/or mirrorlists in
> your yum .repo files via a web browser first.
Today yum works for the first time, no change from yesterday!
But for my situation about network can you help me?
It works for 5 minutes and stops......but yum uses some port? I have a router,
should I have to open some port?
Ok sometimes works sometimes not, sometimes I can reach via browser
http://fedora.redhat.com/download/mirrors/fedora-core-rawhide sometimes not.
Sometimes i can use yum with connection immediately, sometimes I wait for 20
minutes without a response.
Can be related to my network situation?
Marco: it's entirely related to your network situation. I'd suggest refiling a
bug about your network card against the kernel.
oh and unless either of you thinks this is unclosed. I'm going to close it notabug.
Ok if you want to help go to:
(In reply to comment #23)
> oh and unless either of you thinks this is unclosed. I'm going to close it