Bug 76730 - Error message when upgrading to errata ypserv-2.5-2.7x
Error message when upgrading to errata ypserv-2.5-2.7x
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: ypserv (Show other bugs)
7.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Alexander Larsson
Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-25 11:59 EDT by Bernd Bartmann
Modified: 2015-01-07 19:01 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-10-26 08:44:17 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 Bernd Bartmann 2002-10-25 11:59:02 EDT
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 08:44:11 EDT
Also happens for me on Red Hat 7.1
Comment 2 Alexander Larsson 2002-11-05 04:02:15 EST
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 14:09:33 EST
rpm --rebuilddb has indeed solved the problem for me.

Thanks.

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