Bug 244726
Summary: | pirut crashed when attempting most recent update | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | James Bridge <james> | ||||
Component: | pirut | Assignee: | Jeremy Katz <katzj> | ||||
Status: | CLOSED UPSTREAM | QA Contact: | |||||
Severity: | low | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 7 | ||||||
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: | 2007-06-18 21:44:01 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
James Bridge
2007-06-18 19:28:11 UTC
Created attachment 157318 [details]
crash dump plus output from yum
Is this reproducible? If so, can you look at ls -l /var/cache/yum/updates/ It happened twice and then I used yum to update from the console, so it won't happen again. The graphical updater has always worked before. This is what I have just found in updates ls -l //var/cache/yum/updates total 9856 -rw-r--r-- 1 root root 0 2007-06-18 19:56 cachecookie -rw-rw-r-- 1 root root 6782976 2007-06-18 19:33 filelists.sqlite -rw-rw-r-- 1 root root 127520 2007-06-01 03:42 filelists.xml.gz -rw-r--r-- 1 root root 604160 2007-06-01 13:07 filelists.xml.gz.sqlite drwxr-xr-x 2 root root 4096 2007-06-01 10:56 headers drwxr-xr-x 2 root root 4096 2007-06-18 19:38 packages -rw-rw-r-- 1 root root 2166784 2007-06-18 19:57 primary.sqlite -rw-r--r-- 1 root root 26473 2007-06-01 18:23 primary.xml.gz -rw-r--r-- 1 root root 294912 2007-06-02 09:06 primary.xml.gz.sqlite -rw-r--r-- 1 root root 1953 2007-06-16 14:20 repomd.xml Interesting; I suspect that the problem was that a mirror was out of sync. There are some improvements to this upstream for yum 3.2.1; so hopefully that will help keep this from occurring again in the future |