Bug 77700

Summary: up2date reports corrupt database
Product: [Retired] Red Hat Linux Reporter: Need Real Name <empathy>
Component: up2dateAssignee: Adrian Likins <alikins>
Status: CLOSED NOTABUG QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: low Docs Contact:
Priority: medium    
Version: 7.0CC: gafton, mihai.ibanescu
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-08-27 00:27:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Need Real Name 2002-11-12 12:59:17 UTC 
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 22:54:23 UTC 
This looks to be crash related. A `rpm --rebuilddb` should fix it.