Description of problem:
During a yum update one of the i586 (VIA EPIA) boxes had rpm explode
with a message about running some kind of db4 rescue tool (the message
was mostly mangled because whatever blew up also emitted characters
that trashed the terminal font)
Doing an rpm --rebuild fixed it and repeating the update worked fine.
I have saved the rpm database directory after the crash before the
rebuild in case it helps with any debugging if this bug report is useful.
A url to the rpdm tar ball please, and I will look.
Post mortem's are usually uninformative, I need a
reproducer to attempt a fix.
rpmdb tar ball.
Any data loss? is the other interesting question. A --rebuilddb
checks header digests, and will discard any headers that fail.
Sorry got occupied in other stuff. No sign of data loss, will attach
tar ball now
Ok it wont let me , uploading to rpmdb.tar.gz in my Red Hat home dir..
OK, but post mortem rpmdb is hard decipher.
Can you reproduce this on demand, or at least statistical
chance of catching before disks fill up? If so, I can can get
you a version of rpm that enables db logs for display with
Without seeing the time dimension of rpmdb activity, I do not believe
I have a prayer of diagnosing DB_PAGE_NOTFOUND problems in finite time.
Not reproducable at all, feel free to close this sorry it didnt help