search cancel

Troubleshooting a missing library for the CA Single Sign-On (SiteMinder) Policy server and Webagent installation on LINUX with the ldd command.


Article ID: 14435


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On


The ldd command can be used to show you the shared libraries required by any given program. It is useful for figuring out when there is a missing dependency and it can be used to list missing functions and objects.




My Apache start fails after installing the CA Single Sign-On WebAgent.  How do I determine which library is missing?

 > Ignoring invalid environment assignment 'export PATH=/opt/CA/webagent/bin:$PATH': /etc/sysconfig/httpd 

> Starting The Apache HTTP Server... 
> httpd: Syntax error on line 56 of /etc/httpd/conf/httpd.conf: Cannot load /opt/CA/webagent/bin/ into server: cannot open> shared object file: No such file or directory 
> httpd.service: main process exited, code=exited, status=1/FAILURE 
> Ignoring invalid environment assignment 'export PATH=/opt/CA/webagent/bin:$PATH': /etc/sysconfig/httpd 
> kill: cannot find process "" 
> httpd.service: control process exited, code=exited status=1 
> Failed to start The Apache HTTP Server. 
> Unit httpd.service entered failed state. 
> httpd.service failed.


Any LINUX system.


 Verify SELinux has been disabled.  To check that the shared libraries requirements have been installed, run the ldd command on the file and path where the web agent was installed.  For example:

[[email protected] webagent]# ldd /opt/CA/webagent/bin/


Look for the "not found" messages in the output. => (0x00007ffedd1fb000) => /opt/CA/webagent/bin/ (0x00007fd333460000) => /opt/CA/webagent/bin/ (0x00007fd333358000) => /opt/CA/webagent/bin/ (0x00007fd3331cf000) =>  not found => /opt/CA/webagent/bin/ (0x00007fd331e1b000) => /opt/CA/webagent/bin/ (0x00007fd331af0000)  => not found => /opt/CA/webagent/bin/ (0x00007fd33175c000) => /opt/CA/webagent/bin/ (0x00007fd3315fd000) => /lib64/ (0x00007fd3313d9000) => /lib64/ (0x00007fd3311d4000) => /lib64/ (0x00007fd330fcc000) => /lib64/ (0x00007fd330cc4000)


You will notice on many of the other lines the => symbol followed by a path. This is the path to the physical binary.  The hex number is the address where the library will be loaded. You may have also noticed two of the lib files are marked with "not found".