Bug 982262 - rpmdb: page 81: illegal page type or format
rpmdb: page 81: illegal page type or format
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: rpm (Show other bugs)
5.10
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: packaging-team-maint
BaseOS QE Security Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-08 09:56 EDT by Jan Hutař
Modified: 2013-12-17 07:45 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-12-17 07:45:32 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Hutař 2013-07-08 09:56:02 EDT
Description of problem:
Installing zsh package caused rpm DB error.


Version-Release number of selected component (if applicable):
rpm-4.4.2.3-34.el5.ppc


How reproducible:
1 of very very much attempts


Steps to Reproduce:
1. yum -y install zsh


Actual results:
Loaded plugins: aliases, changelog, downloadonly, fastestmirror, filter-data,
              : keys, kmod, list-data, product-id, protect-packages,
              : protectbase, rhnplugin, security, subscription-manager, tmprepo,
              : verify, versionlock
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
This system is receiving updates from RHN Classic or RHN Satellite.
Loading mirror speeds from cached hostfile
Skipping filters plugin, no data
0 packages excluded due to repository protections
Reading version lock configuration
Setting up Install Process
Resolving Dependencies
Skipping filters plugin, no data
--> Running transaction check
---> Package zsh.ppc 0:4.2.6-8.el5 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package     Arch        Version                Repository                 Size
================================================================================
Installing:
 zsh         ppc         4.2.6-8.el5            rhel-ppc-server-5         1.8 M

Transaction Summary
================================================================================
Install       1 Package(s)
Upgrade       0 Package(s)

Total download size: 1.8 M
Downloading Packages:
warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 37017186
Importing GPG key 0x37017186 "Red Hat, Inc. (release key) <security@redhat.com>" from /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction

  Installing     : zsh                                                      1/1rpmdb: page 81: illegal page type or format
rpmdb: PANIC: Invalid argument
rpmdb: PANIC: fatal region error detected; run recovery
rpmdb: PANIC: fatal region error detected; run recovery
rpmdb: PANIC: fatal region error detected; run recovery
rpmdb: PANIC: fatal region error detected; run recovery
rpmdb: PANIC: fatal region error detected; run recovery
rpmdb: PANIC: fatal region error detected; run recovery
rpmdb: PANIC: fatal region error detected; run recovery
rpmdb: PANIC: fatal region error detected; run recovery
rpmdb: PANIC: fatal region error detected; run recovery
rpmdb: PANIC: fatal region error detected; run recovery
rpmdb: PANIC: fatal region error detected; run recovery
rpmdb: PANIC: fatal region error detected; run recovery
rpmdb: PANIC: fatal region error detected; run recovery
rpmdb: PANIC: fatal region error detected; run recovery
rpmdb: PANIC: fatal region error detected; run recovery
 
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "/usr/share/zsh/" records from Dirnames index
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "/usr/share/zsh/4.2.6/" records from Dirnames index
error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30977) getting "/usr/share/zsh/4.2.6/functions/" records from Dirnames index
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Requireversion index using db3 -  (-30977)
error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Provideversion index using db3 -  (-30977)
error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Installtid index using db3 -  (-30977)
error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Sigmd5 index using db3 -  (-30977)
error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Sha1header index using db3 -  (-30977)
error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Filemd5s index using db3 -  (-30977)
rpmdb: PANIC: fatal region error detected; run recovery
rpmdb: PANIC: fatal region error detected; run recovery
rpmdb: PANIC: fatal region error detected; run recovery
rpmdb: PANIC: fatal region error detected; run recovery
[...]


Expected results:
Should work
Comment 3 Florian Festi 2013-12-17 07:45:32 EST
As this can not be reproduced and may be caused by something completely unrelated like a hardware failure I am closing this now. Even if there is a real bug hunting it down for this old version of rpm is not an acceptable use of resources.

Still thanks for reporting. May be we can refer back to this report when more such cases turn up in the future.

Note You need to log in before you can comment on or make changes to this bug.