On Wed, 2004-09-29 at 06:56, Søren Neigaard wrote:
On Tue, 2004-09-28 at 21:27, Paul Howarth wrote:
> up2date has a different configuration file than yum. Try "yum
> check-update" to check for updates, and "yum update" to actually do
the
> update.
Oh maybe the problem is a very different animal, here is what i get if i
run "yum check-update":
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30978) from dbenv->open: DB_RUNRECOVERY: Fatal error,
run database recovery
error: cannot open Packages index using db3 - (-30978)
error: cannot open Packages database in /var/lib/rpm
Traceback (most recent call last):
File "/usr/bin/yum", line 30, in ?
yummain.main(sys.argv[1:])
File "/usr/share/yum/yummain.py", line 163, in main
(log, errorlog, filelog, conf, cmds) = parseCmdArgs(args)
File "/usr/share/yum/yummain.py", line 75, in parseCmdArgs
conf=yumconf(configfile=yumconffile)
File "/usr/share/yum/config.py", line 155, in __init__
self.yumvar['releasever'] = self._getsysver()
File "/usr/share/yum/config.py", line 285, in _getsysver
idx = ts.dbMatch('provides', self.distroverpkg)
TypeError: rpmdb open failed
What can I do about this? Is there a database recovery tool I can use?
That looks like an RPM database problem. Does "rpm -qa" give you a list
of installed RPMs?
Which version of yum are you using ("yum --version"), and which version
of Fedora Linux are you using?
The database can be rebuilt using "rpm --rebuilddb"
If that doesn't help, you may need to "rm /var/lib/rpm/__db.00[123]" and
try "rpm --rebuilddb" again.
Paul.
--
Paul Howarth <paul(a)city-fan.org>