Linux ProLiant Deployment Error Net-SNMP Red Hat Server 3

[Ted Schachter]

Preparing to install A Collection of SNMP Protocol Tools from Net-SNMP for Red H
at Enterprise Linux 3 (x86) v5.1-199
SNMP (Simple Network Management Protocol) is a protocol used for network managem
ent. The Net-SNMP project includes various SNMP tools: The net-snmp RPM package
contains the net-SNMP Protocol plus the cmaX extensions. The net-snmp SRC packag
e includes source for the various SNMP tools: an extensible agent, an SNMP libra
ry, and tools for SNMP agents.
rpmdb: read: 0xb73bafc0, 4096: Input/output error
error: db4 error(5) from dbcursor->c_get: Input/output error
error: error(5) getting "ⁿ~
▀x`;l∩╛¼Yî▓_♦ƒ ┐▄┐σ" records from Filemd5s index
Installation of t

[Michael Garner_1 · Accepted solution]

Ted,
You can receive this error if your RPM database is corrupted. You can recover by using one of two methods.

If you haven't done anything since the error occurred, you can rebuild your rpm database by issuing the "rpm --rebuilddb" command.

If the rebuild fails, then you have to rebuild the database from scratch. To do that,
1) copy the contents of the /var/lib/rpm directory to a backup location.
2) delete the __db.00* files from the /var/lib/rpm. There should be three of them.
3) Re-initialize the RPM database by issuing the "rpm --initdb" command.
4) Rebuild the RPM database by issuing the "rpm --rebuilddb" command.

If all of these fail, then you'll need to restore the /var/lib/rpm directory from a backup copy or contact RedHat on how to repair the damaged RPM database.

The details of the failure in RPM are documented on the Red Hat site at the following URL:
http://www.rhn.redhat.com/errata/RHEA-2004-010.html.

We've added checks in the Linux PSP to minimize the chance of the RPM database corruption. Normally, the cause can be traced to an application that attempts to access the RPM database while the database is locked. This is one of the reasons why we shutdown the agents, health driver, and SNMP during our installation. We know that the HP agents and SNMP attempt to access the RPM database every couple of minutes to update their MIB tables. If an attempt to install software is done while these checks of the RPM database occur, it will randomly cause the corruption you see.

Hope this helps.
Michael Garner
Linux PSP Developer

[Ted Schachter]

Thanks! If I could give you 15 points I would! I appreciate the prompt and accurate reply.

The "rpm --rebuilddb" command worked and I was able to load the software.