Red Hat Bugzilla – Bug 243011
another copy is running as pid
Last modified: 2014-01-21 17:58:12 EST
Whenever I run yum -y upgrade (and not sometimes, not once, but always), I get the error: Existing lock /var/run/yum.pid: another copy is running as pid XXXX. Aborting. # strace -p 2893 Process 2893 attached - interrupt to quit gettimeofday({1181166722, 862123}, NULL) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x91090a8, FUTEX_WAKE, 1) = 0 gettimeofday({1181166722, 862740}, NULL) = 0 poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}], 2, 1000) = 0 gettimeofday({1181166723, 862575}, NULL) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x91090a8, FUTEX_WAKE, 1) = 0 gettimeofday({1181166723, 863162}, NULL) = 0 poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}], 2, 1000) = 0 gettimeofday({1181166724, 862585}, NULL) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x8cd5170, FUTEX_WAKE, 1) = 0 futex(0x91090a8, FUTEX_WAKE, 1) = 0 gettimeofday({1181166724, 863155}, NULL) = 0 poll( <unfinished ...> Process 2893 detached # ps axw|grep yum 2893 ? SN 0:03 /usr/bin/python /usr/sbin/yum-updatesd 4501 pts/1 S+ 0:00 grep yum [root@sb-home ~]# yum -y upgrade Loading "presto" plugin Loading "installonlyn" plugin Loading "fastestmirror" plugin Loading "protectbase" plugin Setting up Presto Reading Presto metadata in from local files Loading mirror speeds from cached hostfile Existing lock /var/run/yum.pid: another copy is running as pid 2893. Aborting.
yum-updatesd in Fedora 8 has been reworked to "hog" the lock file quite a bit less which should help this. Assuming testing continues to go well, I'll be releasing
*** Bug 243186 has been marked as a duplicate of this bug. ***