Bug 189318
Summary: | yum reliably triggers oom-killer | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | James G. Sack <jgsack> |
Component: | yum | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | katzj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-04-19 03:50:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
James G. Sack
2006-04-19 02:30:35 UTC
why'd you install sqlite 3.3.3? b/c that's what's causing the memory overrun. Whoa! How did you pinpoint that? That seemed to be it. I did a rpm --oldpackage back to sqlite-3.1.2-3 (from FC4) and yum works now. To answer your question: I had some thought of upgrading python-sqlite2, and seemed to <accidentally> grab the 2.2.1.3 version from FC5. Then when it griped about needing sqlite3.3, I thought I would be safe installing the FC5 sqlite3.3 if I compiled it in my environment -- guess that may have been an incorrect assumption <grin>. So ... problem is resolved.. ..but I still want to know how you knew? My sincere respects!! And warm thanks for the prompt feedback, too. ..jim It's been reported before. Paul Nasrat discovered it. I just read it. :) |