After installing Web Agent to protect OHS 12C the web server does not start

book

Article ID: 17107

calendar_today

Updated On:

Products

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

Issue/Introduction



We have installed a Web Agent to protect the applications on OHS 12C, and even if the installation and configuration succeeded with no errors, when we try to start the web server it does not start:

Starting server ohs1 ...
Error Starting server ohs1: weblogic.nodemanager.NMException: Received error message from Node Manager Server: [Server start command for OHS server 'ohs1' failed due to: [Failed to start the server ohs1  

Why is this happening? How can we solve this issue?

Environment

Web Agent : R12.52 SP1 CR02OHS 12C (12.1.3)

Resolution

This issue is caused when the SSO module is loaded, and the OHS nodemanager tries to access 127.0.0.1:9999 as a health check to verify if OHS is up, which ends up being protected, and since the authentication is unsuccessful, the nodemanager shuts down and causing the errors when it sends a SIGTERM to startComponent.sh. This is occurring as you are protecting the root of the OHS web server, which includes the /dms/ resource which is being requested in these checks.

Therefore, you need to unprotect the root resource (resource: / and rule: *) to solve the issue.

This is also noted as a known issue in the Release Notes:


Root Directories Cannot Be Protected with Oracle HTTP Server 12c (62038)

https://docops.ca.com/ca-single-sign-on/12-52-sp1/en/release-notes/known-issues-in-release-12-52-sp1/known-issues-in-policy-server-12-52-sp1#KnownIssuesinPolicyServer12.52SP1-OracleIssues