From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208
Netscape/7.02

Description of problem:
 Hello,

Yesterday while I was updating my system the RPM manager went ded.
I can not check my Packages status (add, remove, update). The RPM manager 
starts then disappear. If I try to install any rpm file it also fail. Starts but
then disappear.

I am since yesterday luch time trying to make this work. Could you please help?

I have RH 8.0 and the latest updates until yesterday morning.

I tried to search for a solution but I could not find one.
Bellow is the latest thing I have tried. It seems to be a similar problem, but
is not solving mine.

I can rebuild the database, no error comes back. But still RPM manager
(Packages) does not work. Nor I can install the rpm file by just clicking over
them as I was able to do before.

THANK you in advance.
-JACK
----------------------------------------------------------------


Q. I can't upgrade any packages, run up2date or rpm. What is wrong?

A. The RPM database sometimes gets stuck. One cause of this problem is when a
process working on the RPM database is killed, which leaves lock files in place,
limiting what further processes can do to the database. So, a word to the wise:
make sure such a process really is stuck before killing it - if a process is
using much CPU time (eg. as reported by top) it is probably still doing useful work.

A tip o' the hat to: M A Young <m.a.young@durham.ac.uk> for this summarization.

This has to be repaired manually for rpm to eliminate what are described at
'hangs', and to permit rpm to properly function.

What the nature of the underlying problem is, and how to fix it, are detailed below:

First informally: When a process _is_ so killed [sometimes due to a loss of
power crash, sometimes due to a third party helper application dying without
cleaning up the lock files at exist, sometimes due to an impatient admin], it
will almost always leave some small corruption behind in the RPM 'SleepyCat' db
based database. Usually the simple
rm -f /var/lib/rpm/__db*
rpm -vv --rebuilddb
will remove the lockfiles (which start with that distinctive "__"), and fix the
database damage left behind. [Note: we have added the option -vv here, so that
there is visible progress and lots of detail during the rebuild process -- A
worried admin is often impatient at a lack of visible progress -- this option
causes the rebuild process to be quite verbose.]

But, unfortunately, sometimes more substantive database repair is needed, as
described below the section with Jeff Johnson's email later in this discussion.

Think of a two way linked list (we ignore indices to simplify the presentation)
for RPM Package description items thus:
-> -> -> ->
A B C D E
<- <- <- <-
If we have just a couple of broken links, we do not have any 'orphan chains' and
rpm --rebuilddb can repair things:
-> -> ->
A B C D E
<- <- <-
But if substantial persistent corruption occurs, and is not repaired for a long
time, we might get:
-> ->
A B C D E
<- <-
And it becomes unclear where to re-attach A and B, to the other chain. (Note:
This is an analogy, and does not precisely describe the data structures, rebuild
or dump processes from a formal standpoint.)


What else might cause the problem? Warren Togami has reviewd the trouble ticket
trackers for the Conectiva apt for rpm package, and others (the Ximian updater,
Gerald Teschl's autoupdate), and helped locate some interaction issues which are
being worked on and discussed on the RH rpm-list.

More formally: see the Bugzilla master ticket on this issue, 73097

Separately, a testing release (issued 7 Oct 2002) for an updated RPM is
available at Jeff Johnson's personal ftp site
ftp://people.redhat.com/jbj/test-4.1/ -- Warning: This is NOT a formal Red Hat
QA approved release.


Date: Thu, 8 Aug 2002 09:10:12 -0400
From: Jeff Johnson <jbj@redhat.com>
Subject: Re: rpm database - how to repair it?

On Thu, Aug 08, 2002 at 01:37:52PM +0200, Robert Vojta wrote:
<snip>
> What is the safest way how to repair rpm database
> (if it's corrupted)? I was doing this job a long time
> ago and I forgot the whole process :(

Hmmm, "hangs" in select are usually stale locks. Fix by doing

rm -f /var/lib/rpm/__db*
Otherwise,

All that needs repairing is /var/lib/rpm/Packages, the indices can/will be
rebuilt with rpm --rebuilddb later.

Save a copy just in case:

cd /var/lib
tar czvf /tmp/rpmdb.tar.gz rpm
Verify integrity with

cd /var/lib/rpm
db_verify Packages
If there are any errors, repair by doing

mv Packages Packages-ORIG
db_dump Packages-ORIG | db_load Packages
Read all the headers in Packages by doing

rpm -qa
If you segfault here, make an entry at http://bugzilla.redhat.com and I'll tell
you what to do.

Rebuild the indices

rpm --rebuilddb
------------------------------------
HTH

73 de Jeff

-- 
Jeff Johnson ARS N3NPQ
jbj@redhat.com (jbj@jbj.org)
Chapel Hill, NC


Version-Release number of selected component (if applicable):
Can't use RPM manager nor install RPM files if I click over them. IT worked before.

How reproducible:
Always

Steps to Reproduce:
1.Just call (Packages) under System Settings
2.Just click over any rpm file. It will not install.
3.
    

Actual Results:  The install starts but then stops. No error. The window closes.

Expected Results:  It should show me the status of my installed packages. It
should allow me to install new packages.

Additional info:

I tried the reported solution.
I can rebuild the database.
But it is not helping the RPM manager or installation of new RPM files.