Loaded Plugins:fastestmirror, refresh-PackageKit, securityexistingLock/var/run/yum.pid:another Copy isRunning asPid2135. Another app isCurrently holding the YumLock; Waiting forit to exit ... the other application is: PackageKit Memory: +M RSS (891MB VSZ) started:wed APR1 Geneva: $: - -- Geneva: atago State:sleeping, PID:2135another app isCurrently holding the YumLock; Waiting forit to exit ... the other application is: PackageKit Memory: +M RSS (891MB VSZ) started:wed APR1 Geneva: $: - -- Geneva: -ago State:sleeping, PID:2135another app isCurrently holding the YumLock; Waiting forit to exit ... the other application is: PackageKit Memory: +M RSS (891MB VSZ) started:wed APR1 Geneva: $: - -- Geneva: -ago State:running, PID:2135
This is because there may be other software in the background to perform the installation, occupy the Yum program
1. You can use rm-rf/var/run/yum.pid to force access to Yum Lock, then
2. Wait for Yum to unlock itself (personally think so good, it may be installed in the system necessary other programs, if forced to release, there may be problems)
3. I've had this problem for about 2 minutes, and it's automatically unlocked.
Centos6.5 when installing software using Yum Another app is currently holding the Yum lock; Waiting for it to exit ...