Layer7 Access Management

Expand all | Collapse all

apache failed to start after install the siteminder agent

Jump to Best Answer
  • 1.  apache failed to start after install the siteminder agent

    Posted 07-11-2016 03:50 PM

    Apache :  Server version: Apache/2.4.6 (Red Hat Enterprise Linux)

    Agent :  Product Name=CA SiteMinder Web Agent . FullVersion=12.50.4.913

    I have installed and configured the web agent. Everything seems ok, but when I try to restart the apache using command : apachectl start . It failed with following error :

    httpd: Syntax error on line 56 of /etc/httpd/conf/httpd.conf: Cannot load /opt/nete/webagent/bin/libmod_sm24.so into server: libsmerrlog.so: cannot open shared object file: No such file or directory

     

    I source the environment and 100% sure libmod_sm24.so & libsmerrlog.so are there. when I comment out following two lines from httpd.conf file, i can start apache without issue.

    #LoadModule sm_module "/opt/nete/webagent/bin/libmod_sm24.so"

    #SmInitFile "/etc/httpd/conf/WebAgent.conf"

     

    Thanks in advance for any help.



  • 2.  Re: apache failed to start after install the siteminder agent

    Posted 07-11-2016 04:16 PM

    Have we checked the following

     

    • bit version of apache and bit version of webagent.
    • have we installed and configured webagent with the same user owning apache.
    • also this looks like redhat apache. Have we checked the 12.5 support matrix this combination is supported. I looked up the support matrix and did not find this to be supported (only 2.2.x is supported in both 32 and 64bit on red hat apache).

     

    SAP Portal Services

     

    Attached support matrix

     

     

    Regards

    Hubert



  • 3.  Re: apache failed to start after install the siteminder agent

    Posted 07-12-2016 10:48 AM

    We are running on 7.2. Is that support ?

     

    NAME="Red Hat Enterprise Linux Server"

    VERSION="7.2 (Maipo)"

    ID="rhel"

    ID_LIKE="fedora"

    VERSION_ID="7.2"

    PRETTY_NAME="Red Hat Enterprise Linux Server 7.2 (Maipo)"

    ANSI_COLOR="0;31"

    CPE_NAME="cpe:/o:redhat:enterprise_linux:7.2:GA:server"

    HOME_URL="https://www.redhat.com/"

    BUG_REPORT_URL="https://bugzilla.redhat.com/"

     

    REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"

    REDHAT_BUGZILLA_PRODUCT_VERSION=7.2

    REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"

    REDHAT_SUPPORT_PRODUCT_VERSION="7.2"

    Red Hat Enterprise Linux Server release 7.2 (Maipo)

    Red Hat Enterprise Linux Server release 7.2 (Maipo)



  • 4.  Re: apache failed to start after install the siteminder agent
    Best Answer

    Posted 07-12-2016 11:09 AM

    Hi Jiaxi,

     

    Redhat 7 64 bit is supported with R12.52 SP1 CR01 web agent and later versions. (Please make sure that  your policy server should be r12.52 SP1 or later versions).

     

    Please refer below PSM link for more details.

    https://support.ca.com/phpdocs/7/5262/5262_SiteMinder_12_52_SP1_Platform_Support.pdf

     

    Thanks,

    Sharan



  • 5.  Re: apache failed to start after install the siteminder agent

    Posted 07-12-2016 11:18 AM

    REDHAT 7 OS and embedded Apache -- WebAgent has to be minimum R12.52 SP1 CR02 OR above for Apache 2.4.x.

     

    Capture.JPG



  • 6.  Re: apache failed to start after install the siteminder agent

    Posted 07-12-2016 11:22 AM

    Sharana Sharana

     

    Is there is a reason Policy Server has to be R12.52 SP1 or later? Is there a known issue if Policy Server is R12.5 or R12.51 OR base R12.52?

     

    I am wondering what could be reason of mandating the Policy Server version to use a latest version of WebAgent. According to me WebAgent should work in the capacity of R12.5 or R12.51 OR base R12.52 policy server i.e. no new feature would work. But regular Agent IsProt(), IsAuth() and IsAz() should work.

     

    Regards

    Hubert



  • 7.  Re: apache failed to start after install the siteminder agent

    Posted 07-12-2016 11:34 AM

    Thanks !



  • 8.  Re: apache failed to start after install the siteminder agent

    Posted 07-12-2016 11:52 AM

    So , siteminder web agent 12.50 Cr04 won’t work with Redhat 7 64 bit ?



  • 9.  Re: apache failed to start after install the siteminder agent

    Posted 07-12-2016 12:02 PM

    12.50 Cr04 won’t work with Redhat 7 64 bit = YES.



  • 10.  Re: apache failed to start after install the siteminder agent

    Posted 07-12-2016 12:31 PM

    Hi Jiaxi,

     

    You should always use certified/supported version of web agent first, regardless if you can get it working or not. If OS or web server is not listed in support matrix for your version of agent, then do not install it.

     

    To solve your specific problem, maybe web agent environment variables was not properly loaded in apache start up script. You can modify it follow this tech note.   Or try it on a different machine.

     

    http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1337522.aspx?intcmp=searchresul…

    Let us know if this answers your question.

     

    BTW, try to select CA Single Sign-Oncommunity when asking a question, otherwise it will not show up in the correct forum.

     

    Thanks,

     

    Hongxu



  • 11.  Re: apache failed to start after install the siteminder agent

    Posted 07-21-2016 05:58 PM

    Hi,

    Firstly, make sure if the version used for webagent is supported .

    I had seen this issue before and performing below tasks had solved the issue for me. Hope this helps !

     

    ====================================================

    As root user

    cd /etc/ld.so.conf.d/

    vi apache.conf

     

     

    and add the below 3 lines in apache.conf

    Apache_Home/modules

    Apache_Home/lib

    Siteminder_Home/webagent/bin

     

     

    Once the above is done run the following command.

    /sbin/ldconfig

    =====================================================

    ldconfig creates the necessary links and cache to the most recent shared libraries found in the directories specified on the command line, in the file /etc/ld.so.conf, and in the trusted directories (/lib and  /usr/lib).  The cache is used by the run-time linker, ld.so or ld-linux.so.