Re: PANIC on RPMDB... can't even get version numbers for installed packages...
On Tue, 2006-03-07 at 21:24 -0300, Casimiro de Almeida Barreto wrote: After update done 00:23 08/Mar/2006 the following happened (so I can't even get version for packages...): [r...@terra ~]# yum update 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 rpm issue, what steps did you take up to that point? If you experienced any failures what were they? Please back up your rpmdb (/var/lib/rpm) and create a bugzilla, preferably with the history above. Paul
Re: PANIC on RPMDB... can't even get version numbers for installed packages...
I did the same procedure as I'd do with M$... 1) Reboot the system 2) ftp download.fedora.redhat.com 3) download glibc* 4) rpm -Uvh --force --nodeps glibc-comm* (yeah... after a reboot rpm works) 5) rm glibc-comm* rpm -Uvh --force --nodeps glibc* And everything comes back to life... Paul Nasrat escreveu: On Tue, 2006-03-07 at 21:24 -0300, Casimiro de Almeida Barreto wrote: After update done 00:23 08/Mar/2006 the following happened (so I can't even get version for packages...): [r...@terra ~]# yum update 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 rpm issue, what steps did you take up to that point? If you experienced any failures what were they? Please back up your rpmdb (/var/lib/rpm) and create a bugzilla, preferably with the history above. Paul
Re: PANIC on RPMDB... can't even get version numbers for installed packages...
On Wed, 2006-03-08 at 09:50 -0300, Casimiro de Almeida Barreto wrote: I did the same procedure as I'd do with M$... 1) Reboot the system 2) ftp download.fedora.redhat.com 3) download glibc* 4) rpm -Uvh --force --nodeps glibc-comm* (yeah... after a reboot rpm works) 5) rm glibc-comm* rpm -Uvh --force --nodeps glibc* And everything comes back to life... 1) Use a depsolver eg: yum update glibc this will do the right thing. Updating by hand is really not the way to do things. The fedora documentation projejct explain how to use yum, I suggest you read that. 2) What do you expect from partial forced updates force/nodeps have no use in a casual update. 3) rpm -Uvh glibc-...rpm glibc-commonrpm should work also Basically don't do it like that Paul
