Error: Sm_AgentApi_Init Failed when starting Apache Web Agent
search cancel

Error: Sm_AgentApi_Init Failed when starting Apache Web Agent


Article ID: 140863


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) SITEMINDER CA Single Sign On Agents (SiteMinder)



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

Here is a snippet 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



Web Agent 12.52 SP1 CR09 on Apache 2.2.22 on RedHat 6.10;



Check the following:
A - File: SmHost.conf
  1. policyserver="##.##.##.##,44441,44442,44443"

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

  2. hostconfigobject="HCO_Name_Here"

    Ensure Policy Server has the HCO.

  3. Also, ensure the above 1. IP address exists in the HCO. Or, if FQDN is specified, ensure the name resolution works.
B - File: WebAgent.conf
  1. AgentConfigObject="ACO_Name_Here"Ensure Policy Server has the ACO, it exists in the AdminUI;
C - Other
  1. If SELinux is enabled, change the setting to disabled. See below (1).
In the specific 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.


Additional Information



    Error: Unable to load SiteMinder host configuration in Web Agent