How can I solve the yum. pid lock problem ?, Yum. pid locking Solution

How can I solve the yum. pid lock problem ?, Yum. pid locking Solution

The following error occurs when you use yum list today:

Existing lock/var/run/yum. pid: another copy is runing as pid 2560.

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

The other application is: yum

Memory: 124 m rss (443 mb vsz)

Started: Wed Feb 28 09:12:19 2018-ago

State: TRACE/Stopped, pid: 2560

After the above errors are translated using Google Translate:

Existing lock/var/run/yum. pid: Another copy runs as pid 2560.

Another application is currently holding a lock; wait for it to exit...

Another application is: yum

Memory: 124 mb rss (443 mb vsz)

Start Date: Before Wed Feb 28 09:12:19 2018-

Status: tracing/stopping, pid: 2560

In fact, the above implementation is not a yum list or system error, but an improper operation during use.

Incorrect operation: After the yum list is executed, press Ctrl + z to forcibly stop the printing after the system finishes printing the content. When we execute the yum list again, in this case.

Solution:

Method 1: Delete/var/run/yum. pid command: rm-rf/var/run/yum. pid

Note: delete the yum. pid file and run the yum command again. The yum. pid file will be automatically generated again.

Method 2: restart the system command: shutdown-r now

The above two methods mainly use one of them. If you cannot shut down the system (or server), we recommend that you use "method 1 ".

Note: after using the above solution, if the above "improper operation: yum list --> ctrl + z" occurs again, the above problem will still occur. Therefore, we recommend that you do not use Ctrl + z to forcibly stop printing after using the yum list command.