Bug 116474
Summary: | yum hangs after producing some output | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dan Kelley <dan.kelley> | ||||
Component: | yum | Assignee: | Jeff Johnson <jbj> | ||||
Status: | CLOSED WORKSFORME | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | rawhide | CC: | redhat | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2004-06-10 02:18:04 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: | |||||||
Attachments: |
|
Description
Dan Kelley
2004-02-21 15:49:47 UTC
I'm curious - how long does it hang? Does it hang forever? Could try connecting to a different mirror? I've heard of someone else having similar problems connecting to download.fedora.us before and I'd like to remove some variables. FWIW, I frequently get hangs while reading from socket from download.fedora.redhat.com. Patient persistence, or trying another mirror worksforme. Created attachment 97933 [details]
yum configuration file
Seth Vidal asks how long it hangs. The answer is that I've left it hanging for an hour or so before giving up. Would it help if I left it overnight, to get another data point? It seems pretty clear that I'll get the same results, since (a) the hour I've waited is significantly longer than the 1/4-hour time required to rebuild the RPM database [suggesting to me that there is no yum-related computation of that scale] (b) there are no noticable disk accesses [suggesting to me that the calculation is not doing anything productive] (c) there are no noticable file transfers over my broadband connection [suggesting that the yum work is not limited by a large amount requisite data] In summary, the yum process takes nearly 100% of the CPU without, as I said, printing anything even at the highest 'verbosity' level, noticibly accessing the disk, or accessing the internet. And it uses that CPU resource over a timescale longer than I would expect, based on inferences from similar work. I hope this helps. As I said, I could leave it running overnight, so that I could post here again and report a larger number. But it would seem to be more sensible for me to do other tests, and I'd be happy to do so, if advised. In case it helps, I've attached my /etc/yum.conf file. Maybe I'm just being wrong-headed about it. (I am a yum newbie, but I'm hopeful!) 1. why did you disable keepalive? 2. setting retries to 0 makes it try forever for a failure. I'm betting your retries statement is the source of the problem. -sv I've experienced such hangs also, and am doing right now. Its been going for several hours, but there is no cpu usage, contrary to what Dan is finding. I have experienced such results with all yum versions I have had. Previously it has been due to rpm hanging, but with fc2 dev versions there has been no rpm instance running. The configuration is default appart from some mirrors of fedora.us and my own mirror of the redhat server. kill -9 <process_id> has no effect on the process. Current is latest as of this post. Place of freeze is just after all the list of repositories has been printed. The 1st problem appears to be resolved, use mis-configuration. #2 smells like a stale rpmdb lock because of no cpu usage. Try rm -f /var/lib/rpm/__db* to remove stale locks. Please reopen if stale locks was not the problem. |