Hi

I have precisely the same problem. Except it only shows 1% instead of 2%. The
line numbers are not equal (different versions?):

[me@mypc bin]$ up2date
Traceback (innermost last):
  File "/usr/lib/python1.5/site-packages/libglade.py", line 28, in __call__
    ret = apply(self.func, a)
  File "/usr/share/rhn/up2date/gui.py", line 164, in onStartPageNext
    (self.pkgList, self.skipPkgList) =
up2date.getUpdatedPackageList(pwin.setLabel, pwin.setProgress)
  File "/usr/share/rhn/up2date/up2date.py", line 897, in getUpdatedPackageList
    progressCallback)
  File "/usr/share/rhn/up2date/up2date.py", line 854, in
removeSkipFilesPackagesFromList
    if checkModified(h, f_i):
  File "/usr/share/rhn/up2date/up2date.py", line 773, in checkModified
    installedHdr = installedHeader(hdr['name'])
  File "/usr/share/rhn/up2date/up2date.py", line 162, in installedHeader
    for index in db.findbyname(pkgName):
rpm.error: error reading from database

I have RH 7.0 and all updates. (so up2date is 2.0.6-1).

/Bjarke

I have exactly the same problem with the same error messages.

However I only get the error when the: "Display all packages available, not only
those installed on the system" is checked in my Red Hat Network configuration.

When I try with any other configuration it (seems to) work fine. Returning the
"your system is fully updated" message.

I get something similar after running the GUI version it just sits there stuck
at 3% removing packages.  I then ran it via the command line and got the
following just doing an "up2date --list"  I even upgraded the version of
uptodate that I have to the very latest but its still not working...

Retrieving list of all available packages...

Removing installed packages from list of updates...
100.0%
Removing packages marked to skip from list...
100.0%
Getting headers for available packages...
100.0%
Removing packages with files marked to skip from list...
Traceback (innermost last):
  File "/usr/sbin/up2date", line 382, in ?
    main()
  File "/usr/sbin/up2date", line 366, in main
    sys.exit(batchRun(onlyList, pkgNames))
  File "/usr/sbin/up2date", line 138, in batchRun
    updated, skipped = up2date.getUpdatedPackageList(printit, percent)
  File "/usr/share/rhn/up2date/up2date.py", line 894, in getUpdatedPackageList
    progressCallback)
  File "/usr/share/rhn/up2date/up2date.py", line 851, in
removeSkipFilesPackagesFromList
    if checkModified(h, f_i):
  File "/usr/share/rhn/up2date/up2date.py", line 770, in checkModified
    installedHdr = installedHeader(hdr['name'])
  File "/usr/share/rhn/up2date/up2date.py", line 162, in installedHeader
    for index in db.findbyname(pkgName):
rpm.error: error reading from database

I tried to follow Scoots advice (unchecking "Display all packages available, not
only                those installed on the system") and it worked for me too...

/Bjarke

I also tried unchecking the Display All Packages option. It sort of worked for 
me. It woul get past where it was hanging before and I would be able to select 
the packages. It would download ONE package and then hang with an error message 
stating Invalid Architecture OS type. If I then canceled out and reran up2date, 
it would go past the down load of the last package and verify with the MD5 
thing and download the next package repeating the error. I repeated the 
sequence untill all selected packages were downloaded and it then proceded to 
install them.

Jeff:

Looking at this bug, would you assume these people have corrupted RPM databases?

*** Bug 20392 has been marked as a duplicate of this bug. ***

*** Bug 21071 has been marked as a duplicate of this bug. ***

*** Bug 21071 has been marked as a duplicate of this bug. ***

*** Bug 20332 has been marked as a duplicate of this bug. ***

*** Bug 21071 has been marked as a duplicate of this bug. ***

These users have corrupted RPM databases.  There is no way to fix this
currently.

Actually, it's hard to tell what's up. Could you try doing (db_dump is in the
db3-utils package)

	cd /var/lib/rpm
	db_dump Packages > /dev/null

and report if you see a Berkeley db assertion failed message? Thanks.

*** Bug 22781 has been marked as a duplicate of this bug. ***

I tried to do

[a@b rpm]$ pwd
/var/lib/rpm
[a@b rpm]$ db_dump Packages > /dev/null
[a@b rpm]$

so no errors. After I have updated to the new version of up2date
(up2date-2.1.7-1) the problem resist but has changed. I no more get any error
messages. It goes into some kind of infinite loop (it uses more and more memory
(17 MB after 2 minutes of CPU-time)): 

PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
1207 root      12   0 18768  18M  5320 S    81,0 29,8   2:16 up2date

The window "Update Agent Progress" gets to "Getting headers for available
packages" (progress bar says 100 % - but I think that is a left-over from
"Removing installed packages from list of updates"). Neither the main window nor
the progress window updates (stays gray when something has been in front of
them). When the mouse is over the progress window the cursor is a watch
(indicating that it is working).

It still only a problem if "Display all packages available, not only those
installed on the system" is checked.

*** Bug 24323 has been marked as a duplicate of this bug. ***

*** Bug 22974 has been marked as a duplicate of this bug. ***

*** Bug 23118 has been marked as a duplicate of this bug. ***

*** Bug 23129 has been marked as a duplicate of this bug. ***

*** Bug 23691 has been marked as a duplicate of this bug. ***

Ran db3_dump Packages >/dev/null and got no errors at all. Even if the databases
were corrupted, I would expect rpm --rebuilddb to fix things, but up2date still
fails after doing that.

fixed in rawhide version 2.5 and later.  An errata will be forthcoming at some
point in the future. For now, don't use up2date's "-a" option, and/or turn off
"Retrieve all packages."

*** Bug 33768 has been marked as a duplicate of this bug. ***

My problem looks like this but :
hanging at 100%, in the GUI, after
finishing installation of all packages(400mb)

It actually downloaded and installed everything
but I cannot get back the focus on the OK button.
grayed out, not available :(