When I try to follow the instructions on this page

http://www.fedorafaq.org/#yumconf

I get this message in the terminal window:

Another app is currently holding the yum lock; waiting for it to exit...

As far as I can see, I don't have anything running except the Firefox browser, Kate editor and the terminal. And I stopped the service

yum-updatesd is stopped

So now what? How can I run yum?

And how do I escape out of the terminal window, which just keeps scrolling the same message over and over?

Fer pete sake.

Hit Ctrl-C; that's the key combination to kill any currently running process in a bash shell or terminal.

To find out what's locking up yum, try running:

# ps aux | grep yum

Note the PID number of the process and run this to kill the process:

# kill <insert PID number>

Check to see if the process has been killed by rerunning:

# ps aux | grep yum

If not, rinse and repeat until the process is killed; some processes can be very stubborn.

2 members found this post helpful.

If you have a terminal window open on the desktop and can't kill it by clicking the X button in the top-right, you can use xkill. If you are using KDE, hit ALT+F2, which will call up a run command window. (I'm not sure what it would be in GNOME.) Type in "xkill" and hit enter. The cursor will turn into a skull-and-crossbones. Click on the application you want to kill, and it will kill it.

If you are sure you don't have yum currently running, then something prob'ly happened last time it was run, and it didn't remove the lock. Somewhere in /var, there will be a yum.lock file. I forget exactly where it is and am not on a computer with yum. Search for it, and you should find it. Delete the lock file, and you should be able to run yum again.

su -c 'chkconfig --level 2345 yum-updatesd off' will work. Every other workaround seems to only kill yum-updatesd for runlevel 5. Try yum update after that. Keep in mind that you will no longer be informed that there updates available and as such you will need to check periodically with yum check-update.

The easiest way to find out which process has a lock is to cat /var/run/yum.pid.

While using the kill command to kill that process will stop it, the command probably won't get rid of the yum.pid file. You may have a lock file sitting out there and no process belonging to it. If you enter ps < /var/run/yum.pid and only get the PID TTY TIME CMD headers you can delete the file and the lock will be removed. If you get process information than something is still running and you can track it down. Be careful when killing a yum process, it may be busy doing an rpm update and you can then cause trouble with your rpm database.

If it is yum-updatesd, use the command service yum-updatesd stop. This will be a much nicer way of stopping the process than the kill command. You can use the command service yum-updatesd status to see if it is running. Though typically yum-updatesd will finish checking for updates in a few minutes and free up the lock. Glennzo's way will only stop the yum-updatesd service from starting up on reboots, not stop the current service from running.

As mentioned earlier Cntl+C will stop the current process on a terminal screen.

Bill

1 members found this post helpful.

This is what I get when I run that command:

I have no idea which number is the PID.

Sorry, but you're talking to an extremely rusty linux user here.

When I do that command, no such file is found.

But when I do # service yum-updatesd status as suggested in another post on this thread, it reports that yum-updatesd (pid 2016) is running...

yum did an automatic update earlier today. Does the thing run all the time? And when it is running, does that mean it's 'locked'?

I ran it the other day and did an installation of firefox and didn't have any problem. Now, the last couple of times I've tried to run it or the 'Add/Remove Software' GUI, I've been having problems. 'Add/Remove Software' tries to download the list and then freezes near the end and the list never shows in the window.

I'd rather not kill my automatic update feature if I can get away with it. I've only had Fedora 8 installed for a week or two and I'd like to keep it functioning as intended for as long as possible.

According to # service yum-updatesd status, yum-updatesd is running right now but a search didn't find any yum.lock file in /var

yum-updatesd is a daemon that runs periodically based on the entries in yum-updatesd.conf. See man yum-updatesd.conf for more details. When you did the cat command, nothing had a lock on yum. I installed F8 the other day and yum was locked for quite some time since all the packages were being checked the first time for updates.

I've noticed that things have been taking a lot longer with F8. You may have to just be patient and wait for it to do its thing. On my system pup (package updater) timed out the first time it was used. I followed up with yum update and could see why it had a conniption. The selinux package updates were particularly brutal. pup is now functioning okay with the reduced workload. Perhaps this is one of the reasons they are working on PackageKit for F9. I just launched pirut (Add/Remove Software tool) for first time and can see what you mean. It's acting like the Energizer Bunny right now. I can see the process with the top command still trying to do something and plan on letting it go for a while. I'll post if something traumatic happens.

I agree, they have come out with a great number of updates for F8 already. It would seem impratical to disable yum-updatesd.

Bill

Well now here's a strange one. I tried to run pirut just a few minutes ago and it ran just fine even though yum-updatesd is still running.

So I don't understand this at all. Apparently pirut can run along side yum-updatesd as long as it's in the mood to do so.

So now I'm wondering if I can do a yum install command while yum-updatesd is running.

Anyway, thanks for your help. Sure beats trying to get Billy on the phone.

Now if I sleep on all this information for a couple of nights, maybe I'll get this yum thing figured out.

Thanks again, guys.

yum and pirut can run when yum-updatesd is running as long as it isn't actively doing something. As a daemon it just sits out there and waits until the appropriate time comes around to run active again. When it is actively doing something it will start a yum lock until it finishes. You'll also get a lock when pirut starts and not be able to use yum at the command line.

My first run of pirut completed. It probably took 20 minutes to get to the actual gui where you can pick packages. I wonder if it has to build something the first time it runs? After it came up, I closed it and brought it up again. It came up much faster the second time, maybe 10-15 seconds.

Bill

Is that an option that can be changed in some file? Can it be scheduled to do it's thing at a particular time?

Yeah, I realized that yesterday when I had it open.

Maybe so, but it didn't take that long the first time I ran it.

Yeah, mine came up pretty fast yesterday too when I ran it later in the day, just to see if I could get it to come up. So I guess the 'yum lock' problem basically resolved itself.

Only schedule related piece I know about is the run interval in yum-updatesd.conf, see man yum-updatesd.conf. I do recall, prior to yum-updatesd coming on the scene, people used cron to schedule a job using yum check-update to notify them when updates were available.

Bill

Try this:

Open a terminal.
Become superuser by entering 'su' and then the password.
Then,
# cd /var/run/
# dir
Look for the 'yum.pid' file.
# rm -f yum.pid
# dir
Confirm that the 'yum.pid' file has been deleted.
# yum update
This should re-start your update process.

6 members found this post helpful.