Bug 76730

Summary: Error message when upgrading to errata ypserv-2.5-2.7x
Product: [Retired] Red Hat Linux Reporter: Bernd Bartmann <bernd.bartmann>
Component: ypservAssignee: Alexander Larsson <alexl>
Status: CLOSED CURRENTRELEASE QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: peter.verthez, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-10-26 12:44:17 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 Bernd Bartmann 2002-10-25 15:59:02 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
While updating my Red Hat 7.0 servers to ypserv-2.5-2.7x I get this error message:
[root@rpfirew i386]# rpm -Uvh ypserv-2.5-2.7x.i386.rpm 
Preparing...                ########################################### [100%]
   1:ypserv                 ########################################### [100%]
rpmdb: Suspiciously high nelem of 4294967295 on page 0
Fehler: db4 error(-30979) from db->verify: DB_VERIFY_BAD: Database verification
failed

This happens on all of my RedHat 7.0 servers but on no RedHat 7.2/7.3 server.

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


How reproducible:
Always

Steps to Reproduce:
1. Update a RedHat 7.0 system to ypserv-2.5-2.7x
2. Look at the messages from rpm
3.
	

Additional info:

Comment 1 Peter Verthez 2002-10-26 12:44:11 UTC
Also happens for me on Red Hat 7.1


Comment 2 Alexander Larsson 2002-11-05 09:02:15 UTC
You need to do rpm --rebuilddb to fix this.
This is a known issue with upgrading the rpm in 7.0/1 i think. At least a lot of
people have seen this.



Comment 3 Peter Verthez 2002-11-08 19:09:33 UTC
rpm --rebuilddb has indeed solved the problem for me.

Thanks.