When trying to run yum, I get the following error:
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: yum
I've manually killed each yum process id, but it keeps on occurring (other application is: yum), although the days ago become more recent (used to be 3 days ago, then 1 day ago)..
Any idea what's wrong?
Probably because yum has previously been shutdown uncleanly it's left behind an old lock file.
Try
then restart yum
I'm not a Red Hat user so this will be a bit vague; a quick search suggests that there is a
yum.lock
file somewhere in/var/
- try finding that and/or ayum.pid
(or similar) and eliminate them.Sure. Two
yum
processes can't hold the lock at once, or else you'd get corrupt yum metadata and potentially a corrupt RPM database. If you or another admin leave yum running in another session, you'll get this error. Or, perhaps you have something likeyum-cron
enabled, causing it to periodically be run automatically.EDIT: This is Only valid if your running X
Due to the poise of the question I'd say it may be likely OP, that you have an update window open or may have the package manager open while trying to run yum via shell. This can cause the same result.
hope this helps if the other answers dont.
Do you have
yum-updatesd
set to run on system startup? In my experience this can cause the error you have specified, when it is trying to check for and install updates in the background as you are attempting to use yum from the command line.This can be caused by
yum-updatesd
when a proxy is required but not set inyum.conf
. The service tries to check for updates, gets hung and then just sits there.Also, as previously mentioned, if you're running X and there's a popup about available packages, that can hog the lock.
Easy way to fix this issue