Standalone OHS12c Unable Synchronize configuration Changes (Doc ID 1922930.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle HTTP Server - Version 12.1.2.0.0 and later
Information in this document applies to any platform.

Symptoms

. Oracle HTTP Server (OHS) is configured in a Standalone installation
. Changes made to the configuration files in the staging area are not synchronizing with the runtime configuration area when OHS is started

. Errors on /usr/local/web/domains/<domain>/system_components/OHS/ohs_nm.log during failing startup:

Jul 15, 2014 3:32:56 AM oracle.ohs.plugin.nodemanager.OhsRunCommand execute
INFO: /usr/local/web/OHS12/ohs/bin/httpd.sh httpd.worker -k start -f /usr/local/web/domains/<domain>/config/fmwconfig/components/OHS/instances/ohs1/httpd.conf: exit status = 1
Jul 15, 2014 3:32:56 AM oracle.ohs.plugin.nodemanager.OhsProcessHandler buildProcess
INFO: Check the instance log file for more information: /usr/local/web/domains/<domain>/servers/ohs1/logs/ohs1.log
Jul 15, 2014 3:32:56 AM oracle.ohs.plugin.nodemanager.OhsProcessManagementPlugin$ProcessImpl buildIoException
SEVERE: Failed to start the server ohs1
<Jul 15, 2014 3:32:56 AM EDT> <WARNING> <Server start command for OHS server ohs1' failed due to: Failed to start the server ohs1
Check log file /usr/local/web/domains/<domain>/system_components/OHS/ohs_nm.log
Check log file /usr/local/web/domains/<domain>/servers/ohs1/logs/ohs1.log. Please check Node Manager log and/or server 'ohs1' log for detailed information.>

  

 

Changes

 Some changes were previously performed directly on runtime directory.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms