This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 77700 - up2date reports corrupt database
up2date reports corrupt database
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
7.0
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Adrian Likins
Red Hat Satellite QA List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-12 07:59 EST by Need Real Name
Modified: 2007-04-18 12:48 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-08-26 20:27:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2002-11-12 07:59:17 EST
Description of Problem:

When i run up2date and it downloads updates, up2date exits with an error 
message.

Version-Release number of selected component (if applicable):

up2date-2.8.39-1.7.0

Steps to Reproduce:
1. notice there is an update available
2. run "up2date-nox -u" in a terminal
3. receive error message.

Actual Results:

Installing...
   1:php                    ########################################### 
[100%]
   2:php-manual             ########################################### 
[100%]
rpmdb: Suspiciously high nelem of 4294967294 on page 0
error: db4 error(-30979) from db->verify: DB_VERIFY_BAD: Database 
verification failed

Expected Results:

No error message.

Additional Information:
	
this could be corruption to the database caused by up2date crashing at some 
point?

(It appears that the files are successfully installed, but it is annoying, 
and a sign that something is/was wrong.
Comment 1 Adrian Likins 2003-08-06 18:54:23 EDT
This looks to be crash related. A `rpm --rebuilddb` should fix it.

Note You need to log in before you can comment on or make changes to this bug.