[CentOS] Corrupted RPM DB can't be rebuilt.

[Camron W. Fox]

On 11/01/07 17:27, Barry Brimer wrote:
>> 	I've tried running rpm --rebuild with both the 2.6.18-194.17.4 and
>> 2.6.18-194.26.1 kernels and get a segmentation fault each time.
> 
> You might try moving /var/lib/rpm/__db.00* out of the way and trying to 
> rebuild your rpm DB again.  If that doesn't work, you might want to use 
> strace to see where it gets hung up.
> 
> Barry

Barry,

	It completed the run without a segmentation fault with the strace and
provided the following output errors:

[root at lurker rpm]# strace -f -ff -t -o /var/tmp/rpm_rebuild_strace.txt
rpm --rebuilddb
error: rpmdbNextIterator: skipping h#    1460 Header V3 DSA signature:
BAD, key ID e8562897
error: rpmdbAdd: skipping h#     292 Header V3 DSA signature: BAD, key
ID e8562897
error: rpmdbAdd: skipping h#     316 Header V3 DSA signature: BAD, key
ID e8562897
error: rpmdbNextIterator: skipping h#    1024 Header V3 DSA signature:
BAD, key ID e8562897
error: rpmdbAdd: skipping h#     591 Header V3 DSA signature: BAD, key
ID e8562897
error: rpmdbAdd: skipping h#     592 Header V3 DSA signature: BAD, key
ID e8562897
error: rpmdbAdd: skipping h#     620 Header V3 DSA signature: BAD, key
ID e8562897
error: rpmdbNextIterator: skipping h#     207 Header V3 DSA signature:
BAD, key ID e8562897
error: rpmdbAdd: skipping h#     827 Header V3 DSA signature: BAD, key
ID e8562897
error: rpmdbAdd: skipping h#     870 Header V3 DSA signature: BAD, key
ID e8562897
error: rpmdbAdd: skipping h#     883 Header V3 DSA signature: BAD, key
ID e8562897
rpmdb: page 9866: illegal page type or format
rpmdb: PANIC: Invalid argument
rpmdb: /var/lib/rpm/Packages: pgin failed for page 9866
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal
error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error,
run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error,
run database recovery
[root at lurker rpm]#

Best Regards,
Camron

-- 
Camron W. Fox
Hilo Office
High Performance Computing Group
Fujitsu Management Services of America, Inc.
E-mail:		cwfox at us.fujitsu.com