Solution if you fail to stop the process :
#rm -f /var/run/ 2600
then update your yum
# yum -y update
Make sure that yum-updatesd is started :
# /etc/init.d/yum-updatesd start
su - ( your root password when asked ) yum clean all rpm --rebuilddb
Lots of responses here – but here’s how I get around this issue. Its similar to other posts where one identifies the yum process/es that is holding the lock on yum and killing that PID/s.
NB: This can be dangerous especially if you kill the wrong PID by mistake.
# ps -ef | grep yum root 3185 1207 0 14:47 pts/1 00:00:00 grep yum root 3804 1 0 Jan11 ? 00:00:43 /usr/bin/python -tt /usr/sbin/yum-updatesd # kill -9 3804 # ps -ef | grep yum root 3197 1207 0 14:48 pts/1 00:00:00 grep yum # yum update
Open a terminal.
Become superuser by entering ‘su’ and then the password.
# cd /var/run/
Look for the ‘ ‘ file.
# rm -f
Confirm that the ‘ ‘ file has been deleted.
# yum update
This should re-start your update process.