Cannot upgrade because yum is locked
I can't update to newer version because of yum
When i run:
If I try to kill any of these processes it automatically recreates it.
| Severity | Blocker Message |
|---|---|
| FATAL | Cannot upgrade because yum is locked (/var/run/yum.pid has existed for 10+ minutes). |
[root@servidor ~]# ps aux|grep yum
root 4124 0.0 0.0 250344 8400 ? S Nov20 4:29 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 6676 0.0 0.0 250344 7260 ? S Nov05 15:23 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 9600 0.0 0.0 250344 7956 ? S Nov19 5:11 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 9813 0.0 0.0 250344 25464 ? S 05:19 0:20 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 10151 0.0 0.0 2297224 4660 ? S Nov04 0:00 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 11489 0.0 0.0 112812 968 pts/2 S+ 15:50 0:00 grep --color=auto yum
root 12228 0.0 0.0 250344 7632 ? S Nov18 5:57 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 13372 0.0 0.0 250344 7856 ? S Nov17 6:46 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 14320 0.0 0.0 250344 22164 ? S Nov23 2:31 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 14767 0.0 0.0 250344 7224 ? S Nov13 9:39 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 16810 0.0 0.0 250344 7280 ? S Nov15 8:14 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 19543 0.0 0.0 250344 7236 ? S Nov08 13:16 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 21298 0.0 0.0 250344 7232 ? S Nov10 11:54 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 21799 0.0 0.0 250344 7744 ? S Nov16 7:23 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 22560 0.0 0.0 250344 7240 ? S Nov14 8:51 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 22800 0.0 0.0 250344 7228 ? S Nov07 14:01 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 25844 0.0 0.0 250344 7236 ? S Nov09 12:34 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 25881 0.0 0.0 250344 7232 ? S Nov06 14:35 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 26276 0.0 0.0 250344 22220 ? S Nov24 1:48 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 29922 0.0 0.0 250344 8648 ? S Nov21 3:48 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 30928 0.0 0.0 250344 8780 ? S Nov22 3:13 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update
root 31391 0.0 0.0 250344 22228 ? S Nov25 1:04 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf updateIf I try to kill any of these processes it automatically recreates it.
-
Hello! I would be happy to help. Can you run this command? cat /var/run/yum.pid && echo
You should get a number in response. Can you then use this number for the following command?ps auwfx | grep $number
Obviously replacing $number with the real number. This should help.0 -
Sure: [root@servidor ~]# cat /var/run/yum.pid && echo 10151 [root@servidor ~]# ps auwfx | grep 10151 root 26982 0.0 0.0 112808 972 pts/1 S+ 14:48 0:00 | \_ grep --color=auto 10151 root 10151 0.0 0.0 2297224 4660 ? S Nov04 0:00 /usr/bin/python /usr/bin/yum --assumeyes --color=never --config /etc/yum.conf update0 -
@Ramon Pego It looks like that Yum process has been going since November 4th. You might need to restart your server; would it be possible to try doing so and then test again? 0 -
It worked!! thanks this solved my problem 0 -
I'm glad to hear that fixed the issue! 0
Please sign in to leave a comment.
Comments
5 comments