Sometimes the following happens when you use yum again after an interruption when installing or upgrading some programs with yum
Loaded plugins: fastestmirror
Existing lock /var/run/yum.pid: another copy is running as pid 414.
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: yum
Memory : 55 M RSS (534 MB VSZ)
Started: Mon Jul 20 17:15:20 2020 - 01:43 ago
State : Traced/Stopped, pid: 414
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: yum
Memory : 55 M RSS (534 MB VSZ)
Started: Mon Jul 20 17:15:20 2020 - 01:45 ago
State : Traced/Stopped, pid: 414
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: yum
Memory : 55 M RSS (534 MB VSZ)
Started: Mon Jul 20 17:15:20 2020 - 01:47 ago
State : Traced/Stopped, pid: 414
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: yum
Memory : 55 M RSS (534 MB VSZ)
Started: Mon Jul 20 17:15:20 2020 - 01:49 ago
State : Traced/Stopped, pid: 414
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: yum
Memory : 55 M RSS (534 MB VSZ)
Started: Mon Jul 20 17:15:20 2020 - 01:51 ago
State : Traced/Stopped, pid: 414
Another app is currently holding the yum lock; waiting for it to exit...
The other application is: yum
Memory : 55 M RSS (534 MB VSZ)
Started: Mon Jul 20 17:15:20 2020 - 01:54 ago
State : Traced/Stopped, pid: 414
The reason for this is because yum got stuck during installation and forced out directly, and when you install it again, you are prompted that yum is locked, when you encounter this situation, you can simply delete the yum process.
rm -f /var/run/yum.pid