My Oracle Support Banner

Oracle HTTP Server 12c Fails to Start Via NodeManager with "could not bind to address 0.0.0.0:<PORT>" ERROR (Doc ID 2730849.1)

Last updated on NOVEMBER 23, 2020

Applies to:

Oracle HTTP Server - Version 12.2.1.4.0 to 12.2.1.4.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

After upgrading Forms and Reports 11.1.2.2 to 12.2.1.4 the Oracle HTTP Server fails to start with these errors:

Please enter Node Manager password:
Connecting to Node Manager ...

Successfully Connected to Node Manager.
Starting server ohs1 ...
This Exception occurred at Sat Nov 21 17:20:49 UTC 2020.
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
Check log file <DOMAIN_HOME>/system_components/OHS/ohs_nm.log]. Please check Node Manager log and/or server 'ohs1' log for detailed information.]. Please check Node Manager log for details.
Error: Error occurred while performing nmStart : Error Starting server ohs1 : Received error message from Node Manager Server: [Server start command for OHS server 'ohs1' failed due to: [Failed to start the server ohs1
Check log file <DOMAIN_HOME>/system_components/OHS/ohs_nm.log]. Please check Node Manager log and/or server 'ohs1' log for detailed information.]. Please check Node Manager log for details.
Use dumpStack() to view the full stacktrace :


Exiting WebLogic Scripting Tool.

Done
$



Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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

In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.