libgcc_s.so.1 error when starting apache.

Products

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

Issue/Introduction

Description

After upgrading the Solaris operating system the following error is displayed when starting Apache.

ld.so.1: httpd: fatal: libgcc_s.so.1: open failed: No such file or directory Killed

Solution

This is not a Siteminder problem but is instead caused by Apache's inability to find the libgcc_s.so library.

To troubleshoot this problem; take the following steps:

1. Check the LD_LIBRARY_PATH environment variable.

   
   
   Use echo $LD_LIBRARY_PATH to check the environment variable.
   Check you have reference to /usr/local/lib/ in this variable.
          If this path is not in the variable use the following commands to add it.

   LD_LIBRARY_PATH = $LD_LIBRARY_PATH+"/usr/local/lib/"
   export LD_LIBRARY_PATH

2. Check libgcc_s.so exists

Check libgcc_s.so exists in /usr/local/lib/
if this file does not exist; it can be copied for another system with the same (or similar) operating system.
You can also obtain this file from the GCC binaries ( http://gcc.gnu.org/install/index.html ).

Environment

Release:
Component: SMAPC