Error executing ReportAgent manually in Unix environments.
search cancel

Error executing ReportAgent manually in Unix environments.


Article ID: 17962


Updated On:


CA Virtual Privilege Manager CA Privileged Identity Management Endpoint (PIM) CA Privileged Access Manager (PAM)


While trying to execute ReportAgent manually in debug mode or while trying to immediately send a snapshot of the CA PIM database and any local PMDBs to the queue/snapshots queue on the Distribution Server, at times the following error message appears:

ReportAgent: error while loading shared libraries: cannot open shared object file: No such file or directory


Privileged Identity Manager 12.8, Linux endpoints


The cause for the problem is that the operating system is not able to find the proper location of this shared object file.


  1. Executing 'ldd' against ReportAgent would provide the output of the shared object files / libraries that are loaded, and find as well as any missing shared object files / libraries. For example on a Redhat Linux machine the output would be similar to the output as below.

# ldd ReportAgent =>  (0xffffe000) => not found => /lib/ (0x00d47000) => /lib/ (0xf7fd3000) => /lib/ (0xf7fb9000) => /lib/ (0xf7fb3000) => /lib/ (0xf7f9a000) => /lib/ (0x001a1000) => /usr/lib/ (0x004f6000) => /lib/ (0xf7f71000) => /lib/ (0x00beb000) => /lib/ (0x00de9000) => /lib/ (0xf7f57000)
       /lib/ (0x00bcc000)

  1. The LD_LIBRARY_PATH needs to be set manually pointing to the location where the '' file exists. This setting would be valid for the current session only. In case a new connection is established, the LD_LIBRARY_PATH would have to be set again.
  2. The other way to set the PATH to the shared object file at the Operating System level, follow the below steps
  • Go to the /etc/ directory
  • Create a new .conf file, for example 'ControlMinder.conf'
  • Add the location of the '' file in this file. For example as under
  • Save and exit
  • Next, execute 'ldconfig', if there are no error messages then the OS has updated the location of the shared object file successfully.

Additional Information

Now, executing 'ReportAgent' would not produce the error message and the above procedure in step 3 would be valid for all the users executing the ReportAgent

#ReportAgent -report snapshot
INFO: AC installed directory: /opt/CA/AccessControl
CA Access Control Reporting Agent.


Successfully sent report of seosdb. (id = 1406895034)