Help with RPM rebuilddb

[Oldman]

Hello all

    After updating this morning, I checked the availability of orca with
a yum list updates.  For some reason Yum hung and 1/2 hour later it was
still running with no progress being reported at the terminal.

    I was able to kill the process (holding my breath and crossing the
fingers) by logging in as root at a tty and issuing the appropriate
commands.  Thought I was good to go until I performed the yum update of
orca and though it did update, it immediately gave me 10 pages of
garbage on the screen, followed by some error messages:

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

I attempted to `rpm --rebuilddb` but received:

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)

I got similar errors with --initdb (as expected, but I had to try)


    I googled the error messages and got (as expected) a similar account
on suse, but the suggestions offered, included the use of commands I am
unfamiliar with.

Any ideas of a safe way to get rpm and yum working again?


Scott

[Magnus Larsson]

I like to use "yum clean xxx"
where xxx is a cleaning option.


On 9/22/06, oldman <talbotscott(a)cox.net&gt; wrote:
>  Hello all
>
>      After updating this morning, I checked the availability of orca with
>  a yum list updates.  For some reason Yum hung and 1/2 hour later it was
>  still running with no progress being reported at the terminal.
>
>      I was able to kill the process (holding my breath and crossing the
>  fingers) by logging in as root at a tty and issuing the appropriate
>  commands.  Thought I was good to go until I performed the yum update of
>  orca and though it did update, it immediately gave me 10 pages of
>  garbage on the screen, followed by some error messages:
>
>  rpmdb: PANIC: fatal region error detected; run recovery
>  error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run
>  database recovery
>
>  I attempted to `rpm --rebuilddb` but received:
>
>  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)
>
>  I got similar errors with --initdb (as expected, but I had to try)
>
>
>      I googled the error messages and got (as expected) a similar account
>  on suse, but the suggestions offered, included the use of commands I am
>  unfamiliar with.
>
>  Any ideas of a safe way to get rpm and yum working again?
>
>
>  Scott
>
>  --
>  fedora-test-list mailing list
>  fedora-test-list(a)redhat.com
>  To unsubscribe:
>  https://www.redhat.com/mailman/listinfo/fedora-test-list
>

[Myles Green]

On Fri, 22 Sep 2006 13:59:12 -0700
oldman <talbotscott(a)cox.net&gt; wrote:

>  Hello all
>  
>      After updating this morning, I checked the availability of orca with
>  a yum list updates.  For some reason Yum hung and 1/2 hour later it was
>  still running with no progress being reported at the terminal.
>  
>      I was able to kill the process (holding my breath and crossing the
>  fingers) by logging in as root at a tty and issuing the appropriate
>  commands.  Thought I was good to go until I performed the yum update of
>  orca and though it did update, it immediately gave me 10 pages of
>  garbage on the screen, followed by some error messages:
>  
>  rpmdb: PANIC: fatal region error detected; run recovery
>  error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run
>  database recovery
>  
>  I attempted to `rpm --rebuilddb` but received:
>  
>  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)
>  
>  I got similar errors with --initdb (as expected, but I had to try)
>  
>  
>      I googled the error messages and got (as expected) a similar account
>  on suse, but the suggestions offered, included the use of commands I am
>  unfamiliar with.
>  
>  Any ideas of a safe way to get rpm and yum working again?
>  
>  
>  Scott 
 
I ran into this a while back after interrupting yum. My solution was to
delete the rpm db and the re-run rpm --rebuilddb. It Worked For Me(tm),
YMMV and if it breaks you get to keep all the pieces :-)

HTH, Myles
-- 
The best way to make a fire with two sticks is to make sure one of them
is a match.
		-- Will Rogers

[Oldman]

Myles Green wrote:
>  On Fri, 22 Sep 2006 13:59:12 -0700
>  oldman <talbotscott(a)cox.net&gt; wrote:
>
> >
> > Any ideas of a safe way to get rpm and yum working again?
> >
> >
> > Scott
>   
>  I ran into this a while back after interrupting yum. My solution was to
>  delete the rpm db and the re-run rpm --rebuilddb. It Worked For Me(tm),
>  YMMV and if it breaks you get to keep all the pieces :-)
>  
>  HTH, Myles
>   
Thanks Myles!

I thought about tying that, but was led astray by errors about the
"Packages" file not being read by db3.  Guess I just over-thought that
one by a mile :-)

Scott

[Myles Green]

On Fri, 2006-09-22 at 15:45 -0700, oldman wrote:
>  Myles Green wrote:
>  > On Fri, 22 Sep 2006 13:59:12 -0700
>  > oldman <talbotscott(a)cox.net&gt; wrote:
>  >
>  >>
>  >> Any ideas of a safe way to get rpm and yum working again?
>  >>
>  >>
>  >> Scott
>  >  
>  > I ran into this a while back after interrupting yum. My solution was to
>  > delete the rpm db and the re-run rpm --rebuilddb. It Worked For Me(tm),
>  > YMMV and if it breaks you get to keep all the pieces :-)
>  > 
>  > HTH, Myles
>  > 
>  
>  Thanks Myles!
>  
>  I thought about tying that, but was led astray by errors about the
>  "Packages" file not being read by db3.  Guess I just over-thought that
>  one by a mile :-) 
Hey, no problem, glad to help out. I think we've all been bitten by the
'over-thinking' thing at one time or another ;-)

Myles
-- 
R. M. Green | rmg57 at telus dot net
Calgary AB Canada
Providing Linux and OpenSolaris Solutions to the Calgary Area.

[Tom Diehl]

On Fri, 22 Sep 2006, oldman wrote:

>  Myles Green wrote:
> > On Fri, 22 Sep 2006 13:59:12 -0700
> > oldman <talbotscott(a)cox.net&gt; wrote:
> >
> >>
> >> Any ideas of a safe way to get rpm and yum working again?
> >>
> >>
> >> Scott
> >
> > I ran into this a while back after interrupting yum. My solution was to
> > delete the rpm db and the re-run rpm --rebuilddb. It Worked For Me(tm),
> > YMMV and if it breaks you get to keep all the pieces :-) 
This is like saying "cd / rm -rf *" DO NOT do either one of these!!

>  I thought about tying that, but was led astray by errors about the
>  "Packages" file not being read by db3.  Guess I just over-thought that
>  one by a mile :-) 
DO NOT DELETE THE RPMDB!! It will take you a long time to recreate it!!
rpm --rebuilddb will NOT recreate it. At best it will leave you with an empty
rpmdb.

At that point you will either need to reinstall the system OR spend a lot of
time running rpm --justdb package-name.

The way to correct your problem is to do "rm /var/lib/rpm/__db.00* and then
run rpm --rebuilddb. That will most likely fix your problem.

I have fixed this problem several times with this proceedure. Sometimes it is
sufficient to simply rm the lock files.

Regards,

-- 
Tom Diehl		tdiehl(a)rogueind.com		Spamtrap address mtd123(a)rogueind.com

[Myles Green]

On Fri, 22 Sep 2006 23:33:25 -0400 (EDT)
Tom Diehl <tdiehl(a)rogueind.com&gt; wrote:

>  The way to correct your problem is to do "rm
> /var/lib/rpm/__db.00* and
>  then run rpm --rebuilddb. That will most likely fix your problem. 
>  Myles Green wrote:
> > My solution was to delete the rpm db and the re-run rpm --rebuilddb 
/me scratches head...

Isn't that what I said without all the panic and whoop'la ??

Have another coffee? (not!)

M
-- 
Some people live life in the fast lane.  You're in oncoming traffic.

[Ian Burrell]

On 9/23/06, Myles Green <rmg57(a)telus.net&gt; wrote:
>  On Fri, 22 Sep 2006 23:33:25 -0400 (EDT)
>  Tom Diehl <tdiehl(a)rogueind.com&gt; wrote:
>
>  > The way to correct your problem is to do "rm /var/lib/rpm/__db.00* and
>  > then run rpm --rebuilddb. That will most likely fix your problem.
>
>  > Myles Green wrote:
>  >> My solution was to delete the rpm db and the re-run rpm --rebuilddb
>
>  /me scratches head...
>
>  Isn't that what I said without all the panic and whoop'la ??
>  
You said "delete the rpm db".  The rpm db is everything in
/var/lib/rpm.  Your comment is at best ambiguous and if interpreted
incorrectly can lead catastrophe.  It is best to be clear when that is
a possibility.

 - Ian

[Myles Green]

On Sat, 23 Sep 2006 15:18:29 -0700
"Ian Burrell" <ianburrell(a)gmail.com&gt; wrote:

>  You said "delete the rpm db".  The rpm db is everything in
>  /var/lib/rpm.  Your comment is at best ambiguous and if interpreted
>  incorrectly can lead catastrophe.  It is best to be clear when that is
>  a possibility. 
My mistake, I always understood it to mean the __db.xxx file(s)
inside /var/lib/rpm/. I'll be more concise next time :)

-- 
One is often kept in the right road by a rut.
		-- Gustave Droz

[Tom Diehl]

On Sat, 23 Sep 2006, Myles Green wrote:

>  On Sat, 23 Sep 2006 15:18:29 -0700
>  "Ian Burrell" <ianburrell(a)gmail.com&gt; wrote:
>
> > You said "delete the rpm db".  The rpm db is everything in
> > /var/lib/rpm.  Your comment is at best ambiguous and if interpreted
> > incorrectly can lead catastrophe.  It is best to be clear when that is
> > a possibility.
>
>  My mistake, I always understood it to mean the __db.xxx file(s)
>  inside /var/lib/rpm/. I'll be more concise next time :) 
For the record the /var/lib/rpm/__db* files are the lock files. The other files
as shown below are the rpmdb files. As I said in an earlier post NEVER delete 
the rpmdb files.

(tigger pts2) $ ll /var/lib/rpm
total 60852
-rw-r--r-- 1 rpm  rpm   5632000 Sep 20 09:12 Basenames
-rw-r--r-- 1 rpm  rpm     12288 Sep 15 14:03 Conflictname
-rw-r--r-- 1 rpm  rpm   2392064 Sep 20 09:12 Dirnames
-rw-r--r-- 1 rpm  rpm  10489856 Sep 20 09:12 Filemd5s
-rw-r--r-- 1 rpm  rpm     28672 Sep 20 09:12 Group
-rw-r--r-- 1 rpm  rpm     28672 Sep 20 09:12 Installtid
-rw-r--r-- 1 rpm  rpm     49152 Sep 20 09:12 Name
-rw-r--r-- 1 rpm  rpm  43819008 Sep 20 09:12 Packages
-rw-r--r-- 1 rpm  rpm    331776 Sep 20 09:12 Providename
-rw-r--r-- 1 rpm  rpm    131072 Sep 20 09:12 Provideversion
-rw-r--r-- 1 rpm  rpm     12288 Jul  9 16:11 Pubkeys
-rw-r--r-- 1 rpm  rpm    434176 Sep 20 09:12 Requirename
-rw-r--r-- 1 rpm  rpm    253952 Sep 20 09:12 Requireversion
-rw-r--r-- 1 rpm  rpm     98304 Sep 20 09:12 Sha1header
-rw-r--r-- 1 rpm  rpm     86016 Sep 20 09:12 Sigmd5
-rw-r--r-- 1 rpm  rpm     12288 Sep 15 14:03 Triggername
-rw-r--r-- 1 root root        0 Sep 15 11:07 __db.000
-rw-r--r-- 1 root root    24576 Sep 15 04:07 __db.001
-rw-r--r-- 1 root root  1318912 Sep 15 04:07 __db.002
-rw-r--r-- 1 root root   450560 Sep 15 04:07 __db.003
(tigger pts2) $

Regards,

-- 
Tom Diehl		tdiehl(a)rogueind.com		Spamtrap address mtd123(a)rogueind.com

[cornel panceac]

thnx tom
..

On 9/24/06, Tom Diehl <tdiehl(a)rogueind.com&gt; wrote:
>  On Sat, 23 Sep 2006, Myles Green wrote:
>
>  > On Sat, 23 Sep 2006 15:18:29 -0700
>  > "Ian Burrell" <ianburrell(a)gmail.com&gt; wrote:
>  >
>  >> You said "delete the rpm db".  The rpm db is everything in
>  >> /var/lib/rpm.  Your comment is at best ambiguous and if interpreted
>  >> incorrectly can lead catastrophe.  It is best to be clear when that is
>  >> a possibility.
>  >
>  > My mistake, I always understood it to mean the __db.xxx file(s)
>  > inside /var/lib/rpm/. I'll be more concise next time :)
>
>  For the record the /var/lib/rpm/__db* files are the lock files. The other files
>  as shown below are the rpmdb files. As I said in an earlier post NEVER delete
>  the rpmdb files.
>
>  (tigger pts2) $ ll /var/lib/rpm
>  total 60852
>  -rw-r--r-- 1 rpm  rpm   5632000 Sep 20 09:12 Basenames
>  -rw-r--r-- 1 rpm  rpm     12288 Sep 15 14:03 Conflictname
>  -rw-r--r-- 1 rpm  rpm   2392064 Sep 20 09:12 Dirnames
>  -rw-r--r-- 1 rpm  rpm  10489856 Sep 20 09:12 Filemd5s
>  -rw-r--r-- 1 rpm  rpm     28672 Sep 20 09:12 Group
>  -rw-r--r-- 1 rpm  rpm     28672 Sep 20 09:12 Installtid
>  -rw-r--r-- 1 rpm  rpm     49152 Sep 20 09:12 Name
>  -rw-r--r-- 1 rpm  rpm  43819008 Sep 20 09:12 Packages
>  -rw-r--r-- 1 rpm  rpm    331776 Sep 20 09:12 Providename
>  -rw-r--r-- 1 rpm  rpm    131072 Sep 20 09:12 Provideversion
>  -rw-r--r-- 1 rpm  rpm     12288 Jul  9 16:11 Pubkeys
>  -rw-r--r-- 1 rpm  rpm    434176 Sep 20 09:12 Requirename
>  -rw-r--r-- 1 rpm  rpm    253952 Sep 20 09:12 Requireversion
>  -rw-r--r-- 1 rpm  rpm     98304 Sep 20 09:12 Sha1header
>  -rw-r--r-- 1 rpm  rpm     86016 Sep 20 09:12 Sigmd5
>  -rw-r--r-- 1 rpm  rpm     12288 Sep 15 14:03 Triggername
>  -rw-r--r-- 1 root root        0 Sep 15 11:07 __db.000
>  -rw-r--r-- 1 root root    24576 Sep 15 04:07 __db.001
>  -rw-r--r-- 1 root root  1318912 Sep 15 04:07 __db.002
>  -rw-r--r-- 1 root root   450560 Sep 15 04:07 __db.003
>  (tigger pts2) $
>
>  Regards,
>
>  --
>  Tom Diehl               tdiehl(a)rogueind.com             Spamtrap address
> mtd123(a)rogueind.com
>
>  --
>  fedora-test-list mailing list
>  fedora-test-list(a)redhat.com
>  To unsubscribe:
>  https://www.redhat.com/mailman/listinfo/fedora-test-list
>

[Myles Green]

On Sun, 24 Sep 2006 11:07:31 -0400 (EDT)
Tom Diehl <tdiehl(a)rogueind.com&gt; wrote:

>  For the record the /var/lib/rpm/__db* files are the lock files. The
> other
>  files as shown below are the rpmdb files. As I said in an earlier post
>  NEVER delete the rpmdb files. 
Thanks Tom, lesson learned.

Myles