Fedora This forum is for the discussion of the Fedora Project. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
12-22-2006, 04:23 AM
|
#1
|
Senior Member
Registered: Jun 2004
Location: Spain
Distribution: FC5
Posts: 1,993
Rep:
|
Yum gets stuck
I'm having trouble with yum. No matter how I start it (cli, yumex, software updater) it just hangs.
e.g.
Quote:
sudo yum --disablerepo=livna update
Password:
Loading "installonlyn" plugin
Loading "fedorakmod" plugin
|
It doesn't respond to ctrl+c, closing the terminal, or "killall yum" as root, and if I try to start it again I get an error message about an existing lock that I'm unable to remove.
What can I do to get yum working again?
|
|
|
12-22-2006, 04:29 AM
|
#2
|
LQ Guru
Registered: Mar 2006
Location: Sydney, Australia
Distribution: Fedora, CentOS, OpenSuse, Slack, Gentoo, Debian, Arch, PCBSD
Posts: 6,678
Rep: 
|
I periodically have yum problems in FC5. I don't know what causes it, but killing with signal 9 works. That said, I don't know how to fix the problem except to wait
|
|
|
12-22-2006, 04:34 AM
|
#3
|
Member
Registered: Mar 2004
Location: UK/West Yorkshire/Huddersfield
Distribution: Fedora 7
Posts: 982
Rep:
|
You could try:
sudo yum update --noplugins
or
sudo yum -d 10 update
the latter being the debugging level (which you can alter if you are getting too much garbage. You can then troubleshoot the problem or post back the last few lines where it hangs and I'll be happy to have a look.
Regards
Chris
|
|
|
12-22-2006, 05:46 AM
|
#4
|
Senior Member
Registered: Jun 2004
Location: Spain
Distribution: FC5
Posts: 1,993
Original Poster
Rep:
|
First thing I did was try to kill it with -9 which worked perfectly.
Next thing, I diabled the plugins... and I got a bit further but got stuck again.
Then I tried
Quote:
$ sudo yum -d 10 --disablerepo=livna update --noplugins
|
and got
Quote:
Yum Version: 3.0.1
COMMAND: yum -d 10 --noplugins
Installroot: /
Setting up Update Process
Setting up repositories
Reading repository metadata in from local files
Setting up Package Sacks
Reading Local RPMDB
|
before it got stuck again.
So I thought I'd try , but that has now got stuck as well.
What can I do next?
p.s. I'm unable to kill the rpm --rebuilddb command, even with killall -9 rpm
Last edited by linmix; 12-22-2006 at 05:48 AM.
|
|
|
12-22-2006, 05:48 AM
|
#5
|
Member
Registered: Mar 2004
Location: UK/West Yorkshire/Huddersfield
Distribution: Fedora 7
Posts: 982
Rep:
|
Have you tried:
sudo yum clean all
followed by
sudo yum update
?
|
|
|
12-22-2006, 05:56 AM
|
#6
|
Senior Member
Registered: Jun 2004
Location: Spain
Distribution: FC5
Posts: 1,993
Original Poster
Rep:
|
Quote:
Originally Posted by snecklifter
Have you tried:
sudo yum clean all
followed by
sudo yum update
?
|
I have (with the debug option enabled, and I get stuck in the same place:
Reading Local RPMDB
|
|
|
12-22-2006, 05:58 AM
|
#7
|
LQ Newbie
Registered: May 2006
Distribution: Fedora FC6
Posts: 17
Rep:
|
Here's what worked for me.
rm /var/lib/rpm/__db*
rpm --rebuilddb
yum clean all
Last edited by bfc; 12-22-2006 at 05:59 AM.
|
|
|
12-22-2006, 06:06 AM
|
#8
|
Member
Registered: Mar 2004
Location: UK/West Yorkshire/Huddersfield
Distribution: Fedora 7
Posts: 982
Rep:
|
Sounds like you have a corrupted rpm database thinking about it. I'd be inclined to trash it:
http://www.rpm.org/hintskinks/repairdb/
The page is old still quite relevant.
Regards
Chris
|
|
|
12-22-2006, 08:16 AM
|
#9
|
Senior Member
Registered: Jun 2004
Location: Spain
Distribution: FC5
Posts: 1,993
Original Poster
Rep:
|
Quote:
Originally Posted by bfc
Here's what worked for me.
rm /var/lib/rpm/__db*
rpm --rebuilddb
yum clean all
|
That's basically what's suggested on the page snecklifter referred to and it worked fine. The link also explained how the db may gave got corrupted: nice reading.
Just one last question. I ran yum with the -d 10 option and saw this run across the screen:
Quote:
Building updates object
Traceback (most recent call last):
File "/usr/lib/python2.4/logging/__init__.py", line 731, in emit
msg = self.format(record)
File "/usr/lib/python2.4/logging/__init__.py", line 617, in format
return fmt.format(record)
File "/usr/lib/python2.4/logging/__init__.py", line 405, in format
record.message = record.getMessage()
File "/usr/lib/python2.4/logging/__init__.py", line 276, in getMessage
msg = msg % self.args
TypeError: not enough arguments for format string
|
It doesn't worry me, but it's strange anyway.
Thanks for all your help
|
|
|
12-22-2006, 09:31 AM
|
#10
|
Member
Registered: Dec 2006
Distribution: Debian (Wheeze)
Posts: 391
Rep: 
|
You could also try installing apt utilities as follows.
yum -y install apt
apt-get update
The Y tells yum to say yes to all questions.
|
|
|
12-22-2006, 12:35 PM
|
#11
|
Senior Member
Registered: Jun 2004
Location: Spain
Distribution: FC5
Posts: 1,993
Original Poster
Rep:
|
And now for the next episode...
I used yumex to do a partial update (which went fine) and fired it up again a little later to install something. However, this time yumex never got past the initialization. I decided to wait patiently, but after 3 hours (3!!) I finally killed it. However if I now try to run yum I get a lock error:
Quote:
Existing lock /var/run/yum.pid: another copy is running. Aborting.
|
Both "killall -9 yum" and "killall -9 yumex turn up "no process killed", but I still have a lock and so no yum. (couldn't find a smily pulling out its hair)
|
|
|
12-22-2006, 05:39 PM
|
#12
|
Member
Registered: Mar 2004
Location: UK/West Yorkshire/Huddersfield
Distribution: Fedora 7
Posts: 982
Rep:
|
easy.
sudo rm /var/run/yum.pid
btw, I had all sorts of probs with yumex - FC6 and later have pirut and pup which are a bit better...
|
|
|
12-22-2006, 06:15 PM
|
#13
|
Senior Member
Registered: Jun 2004
Location: Spain
Distribution: FC5
Posts: 1,993
Original Poster
Rep:
|
thanks, that did it.
I've had a look at both purit and Pup, and I can't say I'm impressed. At least as far as ease of use and available options are concerned.
Purit appears to only allow you to add or remove software, not update. Pup doesn't appear to allow me to select which source(s) I wan't to use to provide my updates
I wish yumex wouldn't give me such a pain.
|
|
|
12-22-2006, 06:25 PM
|
#14
|
Member
Registered: Mar 2004
Location: UK/West Yorkshire/Huddersfield
Distribution: Fedora 7
Posts: 982
Rep:
|
You can edit the sources by editing each repository's .repo file under /etc/yum.repos.d/
Change enabled to 0 and then pup will reflect this. If you are regularly having to enable and disable repositories then you need to consolidate. Core, Extras + Livna are usually enough for most. If you need to use ATrpms then enable freshrpms at the same time but exclude Livna permanently - this usually works for me.
Regards
Chris
|
|
|
01-02-2007, 03:26 PM
|
#15
|
LQ Newbie
Registered: Jan 2007
Location: Slovakia
Distribution: Fedora Core 5,6 ; Slackware 10.1
Posts: 2
Rep:
|
How Long it takes?
How long it takes to rebuild a rpm database ? just cca ?
Because I just ended Up with the same problem with yum stucked. I needed to SIGHUP him and deleted "__db.*" files to unlock access to him once more. On my next try I get stucked again. I have done the same thing as before to try to solve it with addition I deleted the whole YUM cache directory { with back-up ofcoarse } and a tryed to install package I desired once again .. and now it is almost 1hour 30min and yum takes still 98% CPU and ended up with
#yum install mplayer
~~output ommited~~
.
.
.
~~output ommited~~
Added 5985 new packages, deleted 0 old in 228.78 sek.
Resolving Dependencies
--> populating transaction ...
---> Downloading Header for mplayer
mplayer-1.0-0.28.pre8.fc5 |=============================| 29kB 00:02
---> package set to to be updated
--> Runnung Transaction test
{{ srr for this non copy paste reply but for a good reason I am unable to copy paste the terminal output. }}
and this I see for about an hour and a half ... what is happening? .. I am thinking that rpm database is corrupted but shoud I leave yum running for a while? or SIGHUP and start rebuilding rpm database?
|
|
|
All times are GMT -5. The time now is 12:37 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|