RHEL3 ES and up2date issue
 

Hello all,

I am experiencing the following issues when attempting to use up2date on a RHEL3 ES server:


[root@<server> tmp]# up2date
rpmdb: Program version 4.2 doesn't match environment version
error: db4 error(22) from dbenv->open: Invalid argument
error: cannot open Packages index using db3 - Invalid argument (22)
error: cannot open Packages database in /var/lib/rpm
Traceback (most recent call last):
File "/usr/sbin/up2date", line 1174, in ?
sys.exit(main() or 0)
File "/usr/sbin/up2date", line 656, in main
ret = sanityChecks(fromDaemon, hasGui)
File "/usr/sbin/up2date", line 288, in sanityChecks
if cfg["useGPG"] and gpgUtils.checkGPGInstallation() == 2:
File "gpgUtils.py", line 31, in checkGPGInstallation
File "gpgUtils.py", line 75, in findKey
File "rpmUtils.py", line 102, in installedHeadersNameVersion
TypeError: rpmdb open failed


[root@<server> tmp]# rpm -q up2date
rpmdb: Program version 4.2 doesn't match environment version
error: db4 error(22) from dbenv->open: Invalid argument
error: cannot open Packages index using db3 - Invalid argument (22)
error: cannot open Packages database in /var/lib/rpm
package up2date is not installed



I tried to install the same version of up2date on the other servers in this farm I was able to update successfully but received the following:

[root@<server> tmp]# rpm -Uvh up2date-4.2.57-2.src.rpm
rpmdb: Program version 4.2 doesn't match environment version
error: db4 error(22) from dbenv->open: Invalid argument
error: cannot open Packages index using db3 - Invalid argument (22)
error: cannot open Packages database in /var/lib/rpm
warning: up2date-4.2.57-2.src.rpm: V3 DSA signature: NOKEY, key ID db42a60e
1:up2date ########################################### [100%]


After this I continue to receive the same errors as before.

Anyone here have any insight into how I can correct this?

Thanks in advance...

I may have just found the answer by reading a post just down from this one in the list... :o I am still open to suggestions though if anyone has one.

how to rebuild the rpm db
 

The proper way of fixing that issue is to essentially rebuild your RPM database. I've had this same problem on 16 RHES3 servers using up2date after installing update4. Here's how to fix it.

cd /var/lib/rpm
rm -rf __db.00*
rpm --rebuilddb (this will recreate the __db.001, __db.002, and __db.003 database files.)

finally run `up2date -u` to update everything.