On Wed, 2004-09-29 at 15: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?
Best regards Søreb
have you tried rebuilding the rpm databases? When I have problems with yum hanging or giving errors I rebuild the databases and it works then.
#cd /var/lib/rpm #rm __db* (or you can move them to somewhere else if this doesn't feel too good) #rpm --rebuilddb
ta, gb