Bug 738461
| Summary: | [abrt] rpm-4.9.1.1-1.fc15: headerVerify: Process /bin/rpm was killed by signal 11 (SIGSEGV) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Yann Droneaud <yann> | ||||||
| Component: | rpm | Assignee: | Panu Matilainen <pmatilai> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 15 | CC: | ffesti, hateya, jnovy, pmatilai | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:60aae6e003ccc78947ebc3b04c212d9db11d2fc3 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-08-06 20:02:51 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
Yann Droneaud
2011-09-14 21:01:24 UTC
Created attachment 523257 [details]
File: backtrace
Created attachment 523258 [details]
Valgrind output
First, take a backup of the rpmdb, something like: # tar czf rpmdb.tar.gz /var/lib/rpm/[A-Z]* Then do the "first-aid" rpmdb recovery step to clear any caches that might've gotten corrupt somehow: # rm -f /var/lib/rpm/__db.* Check if that helped. If not, you can further try: # rpm --rebuilddb If it still segfaults after that, please make the rpmdb backup from the first step available somewhere on the net (you can attach here if you dont have a http/ftp site at hand where you can drop it) for further analysis. (In reply to comment #3) > > Then do the "first-aid" rpmdb recovery step to clear any caches that might've > gotten corrupt somehow: > # rm -f /var/lib/rpm/__db.* > > Check if that helped. After that, rpm does not segfault again. BTW whatever corrupted the environment aside, that rpm is crashing here is of course a bug. The header "blob" headerVerify() is called with is *obviously* buggered here, with ranges completely out of bounds etc. There are at least 3-4 different places in rpm that perform validation on those, but for headers coming out of the rpmdb none of those is executed, so when the rpmdb is returning garbage the verification blows up because of the missing sanity checks on this particular path. Will fix that... (In reply to comment #5) > but for headers > coming out of the rpmdb none of those is executed, so when the rpmdb is > returning garbage the verification blows up because of the missing sanity > checks on this particular path. That would definitely help users : having a clean error message with some tips on how to resolve the error would be better than a segfault (that could lead to other corruption). > Will fix that... Good news. Did you need my copy of corrupted rpmdb ? (In reply to comment #3) > First, take a backup of the rpmdb, something like: > # tar czf rpmdb.tar.gz /var/lib/rpm/[A-Z]* > > Then do the "first-aid" rpmdb recovery step to clear any caches that might've > gotten corrupt somehow: > # rm -f /var/lib/rpm/__db.* > > Check if that helped. If not, you can further try: > > # rpm --rebuilddb > > If it still segfaults after that, please make the rpmdb backup from the first > step available somewhere on the net (you can attach here if you dont have a > http/ftp site at hand where you can drop it) for further analysis. this solution didn't work for me, but running the following: rm -rf /var/lib/rpm/* rm -rf /var/lib/rpm-state/ running on Fedora 16. (In reply to comment #7) > this solution didn't work for me, but running the following: > > rm -rf /var/lib/rpm/* BAD idea, you just deleted the entire rpm database. I hope you have a backup available as otherwise recovering will be somewhere between hard and impossible. This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |