Apache Web Agent on Red Hat does not start up due to Sm_AgentApi_Init Failed.

book

Article ID: 140863

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) SITEMINDER

Issue/Introduction

Apache startup error was observed and it does not start up. User access resulted in HTTP 500 error. 

Here is a snippt from Apache error_log:

[25/Nov/2019:18:51:51] [Info] [CA WebAgent LLAWP] [2792] [LLAWP Monitor: LLAWP has been started.]
[25/Nov/2019:18:51:53] [Error] SiteMinder Agent
        Sm_AgentApi_Init Failed.

        ff ff ff ff
[25/Nov/2019:18:51:53] [Error] SiteMinder Agent
        Failed to initialize the configuration manager.
        LLAWP unable to get configuration, exiting.
[Mon Nov 25 18:51:56 2019] [notice] Apache/2.2.22 (Unix) configured -- resuming normal operations
[25/Nov/2019:18:56:16] [Information] SiteMinder Agent

Environment

Release : r12.52 SP1 CR09

Component : SITEMINDER -WEB AGENT FOR APACHE


Web Server : Apache 2.2.22
OS : RedHat Enterprise Linux 6.10

Resolution

Please check the following.


A - File: SmHost.conf

(1) policyserver="N.N.N.N,44441,44442,44443"

As for the IP address, ensure network access from Agent host to Policy Server.

(2) hostconfigobject="HCO_Name_Here"

Ensure Policy Server has the HCO.

(3) Also, ensure the 1) IP address exists in the HCO. Or, if FQDN is specified, ensure the name resolution works.


B - File: WebAgent.conf

(4) AgentConfigObject="ACO_Name_Here"

Ensure Policy Server has the ACO.


C - Other

If SELinux is enabled, change the setting to disabled. See below.

Article title: LLAWP doesn't start

Article Id: 47280

https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=47280


Note:

In the customer case, the root cause was found that: the HCO had an entry of Policy Server as FQDN but /etc/hosts had a wrong entry, eventually the name resolution failed. The correction resolved the problem.