000014787 - AxM - RSA Agent v3.5 for Apache on Linux Install Error - 'rpm error: Failed dependencies'

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000014787
Applies ToRSA ClearTrust Agent v 3.5 for Apache 1.3
SuSE Linux 9.2
IssueAxM - RSA Agent v3.5  for Apache on Linux Install Error - "rpm error: Failed dependencies"

While attempting to install the RSA 3.5 Apache agent on SuSE 9.2 Linux server, the following errors are displayed:

# rpm -i RSActap13-3.5-linux-2.4-intel.rpm
error: Failed dependencies:
        ld-linux.so.2 is needed by RSActap13-3.5-0
        libc.so.6 is needed by RSActap13-3.5-0
        libdl.so.2 is needed by RSActap13-3.5-0
        libnsl.so.1 is needed by RSActap13-3.5-0
        libpthread.so.0 is needed by RSActap13-3.5-0
        libc.so.6(GLIBC_2.0) is needed by RSActap13-3.5-0
        libc.so.6(GLIBC_2.1) is needed by RSActap13-3.5-0
        libc.so.6(GLIBC_2.1.3) is needed by RSActap13-3.5-0
        libc.so.6(GLIBC_2.2) is needed by RSActap13-3.5-0
        libdl.so.2(GLIBC_2.0) is needed by RSActap13-3.5-0
        libdl.so.2(GLIBC_2.1) is needed by RSActap13-3.5-0
        libpthread.so.0(GLIBC_2.0) is needed by RSActap13-3.5-0
        libpthread.so.0(GLIBC_2.1) is needed by RSActap13-3.5-0

CauseAlthough the absence of these required libraries can always cause this error, another cause can be corruption of the RPM tracking database. This will also cause rpm dependency checks to fail if the required libraries cannot be confirmed.
Resolution

If you are certain all rpms are present, a corrupt rpm tracking database can be corrected by executing the following linux command:

rpm --rebuilddb

Note that rpm is the defacto standard packaging for linux.  It is used for both installing and managing software packages. The RPM database can be queried manually by executing  rpm -qa, and is ordinarily called by installation programs when performing package dependency checks. The command itself can be executed by users, system administrators.  It can also be called by rpm packages themselves for detailed information about the installed software for dependency checks. By rebuilding the RPM database, queries executed will inherently check the integrity of the rpm tracking database to insure the existence of dependency packages (which also includes consistency checksums, version, signing and other important details of dependency packages).

Legacy Article IDa46146

Attachments

    Outcomes