-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Toshiro wrote on Thu, Nov 14, 2002 at 09:07:23PM -0300 :
There doesn't seem to be a recover option for rpm. rpm --rebuilddb gets
that same error message. Anyone know what needs to be done to repair the RPM
database?
I've seen others
I've seen others say this:
rm -f /var/lib/rpm/__*
^^
\_ Did you really mean that (the underscores) or
was it a typo?
Toshiro
$ rpm -ql rpm
[..]
/var/lib/rpm/__db.001
/var/lib/rpm/__db.002
/var/lib/rpm/__db.003
El mar, 12-11-2002 a las 16:50, Todd Lyons escribió:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Guntner wrote on Tue, Nov 12, 2002 at 10:38:04AM -0800 :
There doesn't seem to be a recover option for rpm. rpm --rebuilddb gets
that same error message. Anyone know what needs
Toshiro wrote:
El mar, 12-11-2002 a las 16:50, Todd Lyons escribió:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Guntner wrote on Tue, Nov 12, 2002 at 10:38:04AM -0800 :
There doesn't seem to be a recover option for rpm. rpm --rebuilddb gets
that same error message. Anyone know
I'm getting an error when I try to run rpm on anything. The message I get is:
rpmdb: region error detected; run recovery.
error: db4 error(-30981) from dbenv-open: DB_RUNRECOVERY: Fatal error, run
database recovery
error: cannot open Packages index using db3 - (-30981)
There doesn't seem to
On Tue, 2002-11-12 at 13:38, David Guntner wrote:
I'm getting an error when I try to run rpm on anything. The message I get is:
rpmdb: region error detected; run recovery.
error: db4 error(-30981) from dbenv-open: DB_RUNRECOVERY: Fatal error, run
database recovery
error: cannot open
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Guntner wrote on Tue, Nov 12, 2002 at 10:38:04AM -0800 :
There doesn't seem to be a recover option for rpm. rpm --rebuilddb gets
that same error message. Anyone know what needs to be done to repair the RPM
database?
I've seen others
Todd Lyons grabbed a keyboard and wrote:
David Guntner wrote on Tue, Nov 12, 2002 at 10:38:04AM -0800 :
There doesn't seem to be a recover option for rpm. rpm --rebuilddb gets
that same error message. Anyone know what needs to be done to repair the RPM
database?
I've seen others
