Another App Is Currently Holding The Yum Lock; Waiting For It To Exit...

Thank u soo much....!!

Realy awesome kill -9. thanks everyone

awesome.....wrk for me

kill -9 worked for me, thanks

while installing its showing
Existing lock /var/run/yum.pid: another copy is running. Aborting.


code is showned below

[root - at - localhost ~]# yum install munin-1.4.5.tar.gz

Exist lock /var/run/yum.pid: another copy is running. Aborting.
[root - at - localhost ~]# ps aux | grep yum
root 2338 0.0 0.4 21052 10224 pts/0 T Oct13 0:00 /usr/bin/python /usr/bin/yum install munin-1.4.5.tar.gz
root 2822 0.0 0.8 28592 16524 ? SN 00:58 0:00 /usr/bin/python /usr/share/PackageKit/hel get-updates none
root 3220 0.0 0.4 21052 10192 pts/0 T 01:58 0:00 /usr/bin/python /usr/bin/yum info
root 3222 0.0 0.4 21048 10184 pts/0 T 01:58 0:00 /usr/bin/python /usr/bin/yum info
root 3334 0.0 0.4 21052 10200 pts/0 T 02:12 0:00 /usr/bin/python /usr/bin/yum install munin-1.4.5.tar.gz
root 7792 0.0 0.8 28592 16536 ? SN 05:03 0:00 /usr/bin/python /usr/share/PackageKit/hel get-updates none
[root - at - localhost ~]# kill 2338
[root - at - localhost ~]# ps aux | grep yum
root 2338 0.0 0.4 21052 10224 pts/0 T Oct13 0:00 /usr/bin/python /usr/bin/yum install munin-1.4.5.tar.gz
root 2822 0.0 0.8 28592 16524 ? SN 00:58 0:00 /usr/bin/python /usr/share/PackageKit/hel get-updates none
root 3220 0.0 0.4 21052 10192 pts/0 T 01:58 0:00 /usr/bin/python /usr/bin/yum info
root 3222 0.0 0.4 21048 10184 pts/0 T 01:58 0:00 /usr/bin/python /usr/bin/yum info
root 3334 0.0 0.4 21052 10200 pts/0 T 02:12 0:00 /usr/bin/python /usr/bin/yum install munin-1.4.5.tar.gz
root 7792 0.0 0.8 28592 16536 ? SN 05:03 0:00 /usr/bin/python /usr/share/PackageKit/hel get-updates none
root 7820 0.0 0.0 4200 732 pts/0 S 05:14 0:00 grep yum

hi all i got solution for issues thank u all

add/remove option not working in my linux system (centos)

ok, the only way i could get rid of that PID was to reboot my server, after i reboot, it it was gone:

reboot

Broadcast message from root (pts/0) (Mon Jan 26 12:38:36 2009):

The system is going down for reboot NOW!

so now i send it again, and its gone, i was able to get rid of it by rebooting.

ps aux | grep yum
root      4052  0.0  0.0   4028   716 pts/0    S+   13:00   0:00 grep yum

if you see on the output of your command, the message says "another copy is running as pid 19562" so all you have to do is send this command:

i made a typo on my command, and now i am getting this error:

i send the command: Then i noticed it got stuck it wasnt doing anything so i tried the control-c to stop it, but that wasnt doing anything, so then i hit the break key on my keyboard and that stopped it i got the command prompt again...

Then i got this message after i send the correct command:

[root]# yum list lynx
Existing lock /var/run/yum.pid: another copy is running as pid 19562.
Another app is currently holding the yum lock; waiting for it to exit...
Another app is currently holding the yum lock; waiting for it to exit...
Another app is currently holding the yum lock; waiting for it to exit...
Another app is currently holding the yum lock; waiting for it to exit...
Another app is currently holding the yum lock; waiting for it to exit...
Another app is currently holding the yum lock; waiting for it to exit...

so now i followed your instructions and i send your command:
What's the PID on this output?

[root]# ps aux | grep yum
root      2576  0.0  0.3  22620 11880 ?        SN   Jan25   0:01 /usr/bin/python /usr/sbin/yum-updatesd
root     19562  0.1  0.3  21352 11040 pts/0    T    12:21   0:00 /usr/bin/python /usr/bin/yum info lynx
root     19622  0.0  0.0   4028   720 pts/0    S+   12:24   0:00 grep yum

good i got the solution for ur blog thanks...

i dont know if this is good advise, but i found this, just google it

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:



note the pid number of the process and run this to kill the process:



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



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

if that doesnt work, try this command:

pkill -9 pid

eg:

pkill -9 3567