More RPM Database Corruption and YUM Problems

[jackfruit501]

Hi Hlingler,

When I yum update F10 today I get the following error

sudo yum -y update
Loaded plugins: allowdowngrade, fastestmirror, kernel-module, presto,
: priorities, protect-packages, protectbase, refresh-packagekit,
: security
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30975) from dbenv->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db3 - (-30975)
error: cannot open Packages database in /var/lib/rpm
Traceback (most recent call last):
File "/usr/bin/yum", line 29, in <module>
yummain.user_main(sys.argv[1:], exit_code=True)
File "/usr/share/yum-cli/yummain.py", line 309, in user_main
errcode = main(args)
File "/usr/share/yum-cli/yummain.py", line 157, in main
base.getOptionsConfig(args)
File "/usr/share/yum-cli/cli.py", line 189, in getOptionsConfig
self.conf
File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 652, in <lambda>
conf = property(fget=lambda self: self._getConfig(),
File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 239, in _getConfig
self._conf = config.readMainConfig(startupconf)
File "/usr/lib/python2.5/site-packages/yum/config.py", line 794, in readMainConfig
yumvars['releasever'] = _getsysver(startupconf.installroot, startupconf.distroverpkg)
File "/usr/lib/python2.5/site-packages/yum/config.py", line 867, in _getsysver
idx = ts.dbMatch('provides', distroverpkg)
TypeError: rpmdb open failed

Yesterday on yum update I had

rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30975) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30975) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30975) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery

Any help would be most welcome.

Jack

[Hlingler]

Sure looks like a plain old corrupt RPM database. Fix it: http://www.rpm.org/wiki/Docs/RpmRecovery

Try removing the stale locks first, then if that doesn't fix, do the whole repair.

Was there some power failure or such recently that interrupted YUM or RPM before they had completed a transaction ? That's usually what corrupts the RPM database.

V

[jackfruit501]

Hi Hlingler,

I have fixed the corrupted RPM database as in the RpmRecovery wiki.
Yum update after that , I get the error as follows :

$ sudo yum clean all
Loaded plugins: allowdowngrade, fastestmirror, kernel-module, presto,
: priorities, protect-packages, protectbase, refresh-packagekit,
: security
Cleaning up Everything
Cleaning up list of fastest mirrors
$ sudo yum clean metadata
Loaded plugins: allowdowngrade, fastestmirror, kernel-module, presto,
: priorities, protect-packages, protectbase, refresh-packagekit,
: security
0 metadata files removed
0 sqlite files removed
0 metadata files removed
$ sudo yum -y update
Loaded plugins: allowdowngrade, fastestmirror, kernel-module, presto,
: priorities, protect-packages, protectbase, refresh-packagekit,
: security
Determining fastest mirrors
Could not retrieve mirrorlist http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=i386 error was
[Errno 4] IOError: <urlopen error (-3, 'Temporary failure in name resolution')>
Error: Cannot find a valid baseurl for repo: fedora
$ sudo yum -y update
Loaded plugins: allowdowngrade, fastestmirror, kernel-module, presto,
: priorities, protect-packages, protectbase, refresh-packagekit,
: security
Loading mirror speeds from cached hostfile
Error: Cannot find a valid baseurl for repo: fedora

Thanks for the quick response.

Jack

[Hlingler]

Could not retrieve mirrorlist http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=i386 error was
[Errno 4] IOError: <urlopen error (-3, 'Temporary failure in name resolution')>
Error: Cannot find a valid baseurl for repo: fedora

This looks like a parsing error: '$releasever' was supposed to be replaced by '11' (or 10, 9, or whatever), just like '$arch' is replaced by 'i386'. I don't know why.

Please post files:
/etc/yum.repos.d/fedora.repo
/etc/fedora-release

V

P.S. I'm moving these posts to a new thread, since this problem is not the same as the OP.

[jackfruit501]

Hi Hlingler,

I have corrupted the whole F10 when I tried to fix the broken packages using synaptic. Anyway I had a clone of the harddisk done about 2 weeks ago. Now everything is OK. The moral is not to disconnect while updating and also not to mix yum with synaptic!

Thanks Hlingler once again.

Jack