Bug 244178 – yum-updatesd and rpmq consume 100% CPU, unresponsive

Bug 244178 - yum-updatesd and rpmq consume 100% CPU, unresponsive

Summary:	yum-updatesd and rpmq consume 100% CPU, unresponsive

Status:	CLOSED DUPLICATE of bug 245389

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	rpm (Show other bugs)
Sub Component:
Version:	7
Hardware:	i386 Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Paul Nasrat
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-06-14 08:36 EDT by Liam Dennehy
Modified:	2007-11-30 17:12 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-06-22 20:13:29 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Liam Dennehy 2007-06-14 08:36:04 EDT

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):
rpm: 4.4.2
yum-updatesd: unknown (rpm query hangs)

How reproducible:
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
3.
  
Actual results:
python /usr/sbin/yum-updatesd consumes all available CPU time
rpmq consumes all available CPU time

Expected results:
yum-updatesd: update query occurs without intervention
rpmq: query results returned immediately

Additional info:

Comment 1 Jeff Johnson 2007-06-15 22:45:40 EDT

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.

Comment 2 Liam Dennehy 2007-06-22 20:14:06 EDT


*** This bug has been marked as a duplicate of 245389 ***

Note You need to log in before you can comment on or make changes to this bug.