My Oracle Support Banner

Restart Fails Due to Inability of Service to Bind to Address Port ("no listening sockets available") on Oracle HTTP Server(OHS) (Doc ID 2497618.1)

Last updated on FEBRUARY 26, 2019

Applies to:

Oracle Compute Cloud Service - Version N/A and later
Oracle HTTP Server - Version 12.2.1.3.0 and later
Information in this document applies to any platform.
Microsoft Windows x64 (64-bit) on Oracle Public Cloud
- Windows 2012 Server running OHS (version 12.2.1.3.0) on Oracle Cloud Infrastructure.
- This issue may also show up on Windows instances running other applications such as Microsoft SQL server
- Changing the application's defined port does not solve the problem

Symptoms

* When starting Oracle HTTP Server(OHS)  it will start fine on the first attempt. However, if OHS was stopped for any reason, subsequent attempts to start it again fails with errors indicating the OHS port is still in use.
* In order to get OHS started again, a server reboot is required which is a major inconvenience as well as cause for unnecessary service unavailability.

- The netstat shows the port as not in use, however the Microsoft network monitor app shows the port is in use even though no indication is given of the service is actually using that port.
Below are sample entries from the MS network monitor app:

6:22:30 PM 1/10/2019 0.8624951 nnn.nnn.nnn.51 nnn.nnn.nnn.3 TCP TCP:Flags=......S., SrcPort=35458, DstPort=7793, PayloadLen=0, Seq=2597351969, Ack=0, Win=26880 ( Negotiating scale factor 0x7 ) = 26880 {TCP:18, IPv4:17}
6:22:30 PM 1/10/2019 0.8625310 nnn.nnn.nnn.3 nnn.nnn.nnn.51 TCP TCP:Flags=...A.R.., SrcPort=7793, DstPort=35458, PayloadLen=0, Seq=0, Ack=2597351970, Win=0 {TCP:18, IPv4:17}
 
22626 6:24:11 PM 1/10/2019 101.6095158 nnn.nnn.nnn.99 nnn.nnn.nnn.3 TCP TCP:Flags=......S., SrcPort=4228, DstPort=7793, PayloadLen=0, Seq=488193235, Ack=0, Win=65535 ( Negotiating scale factor 0xd ) = 65535 {TCP:616, IPv4:35}
22627 6:24:11 PM 1/10/2019 101.6095384 nnn.nnn.nnn.3 nnn.nnn.nnn.99 TCP TCP:Flags=...A.R.., SrcPort=7793, DstPort=4228, PayloadLen=0, Seq=0, Ack=488193236, Win=0

ERROR
-----------------------
The OHS Node Manager log file (ohs_nm.log) contains entries similar to the following:

D:\oracle\*******\********\********\ohs\servers\ohs1\logs\ohs1.log>
<2019-01-10 17:42:45> <INFO> <OHS-4020> <Stopping server ohs1>
<2019-01-10 17:42:45> <INFO> <OHS-0> <Running D:\oracle\*******\ohs\bin\launch.exe D:\oracle\*******\ohs\bin\httpd.exe -DOHS_MPM_WINNT -d D:/oracle/*******/********/********/ohs/config/fmwconfig/components/OHS/instances/ohs1 -k shutdownconsole -f D:\oracle\*******\********\********\ohs\config\fmwconfig\components\OHS\instances\ohs1\httpd.conf>
<2019-01-10 17:42:46> <INFO> <OHS-0> <D:\oracle\*******\ohs\bin\launch.exe D:\oracle\*******\ohs\bin\httpd.exe -DOHS_MPM_WINNT -d D:/oracle/*******/********/********/ohs/config/fmwconfig/components/OHS/instances/ohs1 -k shutdownconsole -f D:\oracle\*******\********\********\ohs\config\fmwconfig\components\OHS\instances\ohs1\httpd.conf: exit status = 0>
<2019-01-10 17:42:46> <INFO> <OHS-4005> <Check the instance log file for more information: D:\oracle\*******\********\********\ohs\servers\ohs1\logs\ohs1.log>
<2019-01-10 17:42:48> <INFO> <OHS-0> <The server 'ohs1' with process id 11372 is no longer alive; waiting for the process to die.>
<2019-01-10 17:42:49> <INFO> <OHS-0> <Server was killed>
<2019-01-10 17:43:27> <INFO> <OHS-0> <Domain initialized for D:\oracle\*******\********\********\ohs>
<2019-01-10 17:44:13> <INFO> <OHS-4018> <Starting server ohs1>
<2019-01-10 17:44:13> <INFO> <OHS-0> <Running D:\oracle\*******\ohs\bin\launch.exe D:\oracle\*******\ohs\bin\httpd.exe -DOHS_MPM_WINNT -d D:/oracle/*******/********/********/ohs/config/fmwconfig/components/OHS/instances/ohs1 -f D:\oracle\*******\********\********\ohs\config\fmwconfig\components\OHS\instances\ohs1\httpd.conf>
<2019-01-10 17:44:13> <INFO> <OHS-0> <(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted.  : AH00072: make_sock: could not bind to address 0.0.0.0:7793>
<2019-01-10 17:44:13> <INFO> <OHS-0> <AH00451: no listening sockets available, shutting down>
<2019-01-10 17:44:13> <INFO> <OHS-0> <AH00015: Unable to open logs>
<2019-01-10 17:44:14> <SEVERE> <OHS-0> <D:\oracle\*******\ohs\bin\launch.exe D:\oracle\*******\ohs\bin\httpd.exe -DOHS_MPM_WINNT -d D:/oracle/*******/********/********/ohs/config/fmwconfig/components/OHS/instances/ohs1 -f D:\oracle\*******\********\********\ohs\config\fmwconfig\components\OHS\instances\ohs1\httpd.conf: exit status = 1>
<2019-01-10 17:44:14> <INFO> <OHS-4005> <Check the instance log file for more information: D:\oracle\*******\********\********\ohs\servers\ohs1\logs\ohs1.log>
<2019-01-10 17:44:14> <SEVERE> <OHS-0> <Failed to start the server ohs1>


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Stop OHS then attempt to restart it results in a failure to start with the indication that the application cannot bind to its defined port ("could not bind to address") errors appearing in the OHS log files.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Rebooting the server when the real goal is to restart OHS is a major inconvenience as well as cause for unnecessary service unavailability.

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!


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