Bug 101161
Summary: | rpm 4.2 --rebuilddb hangs and rpm database is corrupted | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Jari Aalto <jari.aalto> |
Component: | rpm | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED WORKSFORME | QA Contact: | Mike McLean <mikem> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 9 | ||
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: | 2003-08-19 16:03:06 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
Jari Aalto
2003-07-29 18:59:37 UTC
No, there are no "custon" utilities, only internal Berkeley db-4.1.25 compiled with --with-uniquename=_rpmdb to a) make an rpm build easier (i.e. don't have to configure/build db4) b) unique symbols to avoid symbol collisions. In fact, this is what was recommended by Sleepycat. All I can tell from above is that you have some damage, I'd need the xxxxx to guess what was damaged. Meanwhile, fix is probably possible if you give me a pointer (i.e. URL, attachments won't work) to the earliest possible (i.e. least "fixed") version of /var/lib/rpm that you still have. Further info: As the problem persistested I did the following with standard RH 9: 1. Deletd /var/lib/rpm/Packages 2. rpm --initdb .. Then I used an awk script to extract the /roor/install.log file to get the list of installed files (that were supposed to be in RPM database) and make a shell for-loop to manually install all files again into newly created RPM DB. cd /tmp/redhat/all-rpms-here/ (Downloaded from a Mirror site) for $package in ....script to feed names ... do rpm --nodeps --force -Uvh $package done It took a night to install all rPMS to "database" again, although the actual packages were already in my machin. The informationwas just lost. However even this method did not restore Database. rpm -qa locked up as like before. After that I reinstalled whole RH9. I can't provide much further details for this error situation any more, so you can close this bug report after this message. However, I do that the original situation left in my Debian disk, 1. The initially corrupted database (Packages) 2. The one that was result of the db_dump + db_load to try to fix it, which gave the errors I mentioned (Packages.ok) You can download these from below. Hopefully you get something out of those to prevent similar lock up and corruptions in the future. http://tierra.dyndns.org:81/rh-data This link will cease to exist after some time after I have posted it. This problem appears resolved. There's little that can be identified from looking at the database post mortem. The messages indicate lots of headers failing simple sanity checks. How that information got in the database cannot be determined. |