Red Hat Bugzilla – Bug 244178
yum-updatesd and rpmq consume 100% CPU, unresponsive
Last modified: 2007-11-30 17:12:07 EST
Description of problem:
yum-updatesd in high-CPU loop, does not respond to regular kill command, SIGKILL
terminates process. When I tried to use rpm -qi to query version number for this
bug report, rpmq got stuck in a high-CPU loop instead. Again, SIGKILL is only
way to terminate rpmq.
Version-Release number of selected component (if applicable):
yum-updatesd: unknown (rpm query hangs)
each time I run rpm command. Has happened multiple times before, until I
discovered SIGKILL reboot was only remedy.
Steps to Reproduce:
1. Leave box on for indeterminate amount of time
2. let yum-updatesd start
python /usr/sbin/yum-updatesd consumes all available CPU time
rpmq consumes all available CPU time
yum-updatesd: update query occurs without intervention
rpmq: query results returned immediately
After SIGKILL, you *must* do
rm -f /var/lib/rpm/__db*
or you will have a stale lock.
Otherwise yum-updatesd behavior has nothing to do with rpm.
*** This bug has been marked as a duplicate of 245389 ***