[SOLVED] yumbackend.py taking up 98% of the CPU?

jbuckley2004 · #1 2nd December 2011, 05:26 AM

Sort of. According to top it's taking up 98% of 1 CPUs for approximately two minutes of every 20 or so, cycling between all four CPUs. Never seen anything quite like this before.

This is in F16 running on an AMD quad-core.

I see that yumbackend.py has been brought up several times, always in conjunction with yum errors. I haven't been experiencing those, just the weird cpu utilization. It's making my fan go bonkers.

Has anyone else experienced this, and is there a known solution?
Thanks.

smsmith · #2 3rd December 2011, 03:32 AM

I've noticed this, too, because I can't use yum when it's happening. I can kill the process but it comes back on its own. Not sure on the frequency.

jbuckley2004 · #3 3rd December 2011, 03:50 AM

Thanks for the feedback, smsmith.

The frequency varies. In fact, the problem, such as it is, hasn't shown up today at all. I'll report back here if I learn anything new about the situation.

smr54 · #4 3rd December 2011, 04:01 AM

It may be a packagekit issue. There was a recent thread about disabling packagekit, which, I think, uses yum as the backend and is becoming harder to disable.

http://forums.fedoraforum.org/showthread.php?t=273225

didier83 · #5 3rd December 2011, 08:36 AM

I solved the problem the "hard" way:

I renamed /usr/share/PackageKit/helpers/yum/yumBackend.py to /usr/share/PackageKit/helpers/yum/yumBackend.py;orig

Sure it is not a professional choice, but apparently it works

.

jbuckley2004 · #6 3rd December 2011, 01:45 PM

Well, that's one way

Thanks.

dwarthog · #7 3rd December 2011, 04:16 PM

Some new fixes out in the repos this morning. The details on the KDE ones I looked at indicated something about APPER waking up every 5mins?, or something along those lines and a fix for that.

Ok, went and found the info.

https://bugzilla.redhat.com/show_bug.cgi?id=752564

Bug 752564 - Apper wakes up yumBackend.py every 5 minutes

jbuckley2004 · #8 3rd December 2011, 04:30 PM

Yes, the bug report matches what I've been experiencing, including the checking for updates every 5 minutes. I noticed it happening once yesterday, just as updates were announced by packagekit.

I've updated my system with the latest. I'll mark this as solved in 24 hours or so, assuming the problem doesn't reoccur.

Added: Okay - it's been a day and since Friday evening's updates, I've seen no further instances of the CPU pegging the meter like it was. I think it's safe to mark this thread "solved".