Yum has crapped the bed again. Last time was a year ago where the
database also destroyed itself. The claim at the time was this was a
hardware problem. Well, if it is, it only seems to effect yum.
Occam's razor says "got another guess?". It certainly feels like
yum/rpm has a software problem with respect to maintaining the
database.
Has anyone ever recovered from this state without clearing the
database and reinstalling all the rpm's?
$ yum list
Loading "installonlyn" plugin
Loading "fastestmirror" plugin
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbenv->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db3 - (-30977)
error: cannot open Packages database in /var/lib/rpm
Traceback (most recent call last):
File "/usr/bin/yum", line 29, in ?
yummain.main(sys.argv[1:])
File "/usr/share/yum-cli/yummain.py", line 82, in main
base.getOptionsConfig(args)
File "/usr/share/yum-cli/cli.py", line 205, in getOptionsConfig
errorlevel=opts.errorlevel)
File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 125, in doConfigSetup
self.conf = config.readMainConfig(startupconf)
File "/usr/lib/python2.4/site-packages/yum/config.py", line 598, in readMainConfig
yumvars['releasever'] = _getsysver(startupconf.installroot, startupconf.distroverpkg)
File "/usr/lib/python2.4/site-packages/yum/config.py", line 661, in _getsysver
idx = ts.dbMatch('provides', distroverpkg)
TypeError: rpmdb open failed
-wolfgang
--
Wolfgang S. Rupprecht http://www.wsrcc.com/wolfgang/
