Bug 966025
Summary: | [abrt] yum-3.4.3-91.fc19: rpmsack.py:38:<module>:ValueError: bad marshal data (string size out of range) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Lalatendu Mohanty <lmohanty> | ||||||||
Component: | yum | Assignee: | Packaging Maintenance Team <packaging-team-maint> | ||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 19 | CC: | admiller, ffesti, firas.alkafri, lmohanty, packaging-team-maint, tim.lauridsen, zpavlas | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | abrt_hash:a9fea10b35c31dc8b2aaaa0ebc7963e5861527d4 | ||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2013-05-24 10:40:49 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
Lalatendu Mohanty
2013-05-22 10:01:21 UTC
Created attachment 751630 [details]
File: backtrace
Created attachment 751632 [details]
File: core_backtrace
Created attachment 751635 [details]
File: environ
Without --downloadonly, Yum keeps rpmdb open when downloading packages. During that, applydeltarpm is spawned to rebuild RPMs from DRPMs, and it acesses rpmdb, too. But IMO this should not cause any problems, even if no locking was involved (two readers case). Anyway, rpmdb is corrupted. Does rpm --rebuilddb help? *** This bug has been marked as a duplicate of bug 924417 *** "rpm --rebuilddb " fixes the issue Though "rpm --rebuilddb " fixes the issue. Thanks for the work around. But we still need to fix the root cause |