My Oracle Support Banner

After Applying Microsoft Security Update KB4338824 Oracle HTTP Server Start Failed With "could not bind to address 0.0.0.0:8888" and "Unable to open logs". (Doc ID 2429939.1)

Last updated on AUGUST 01, 2018

Applies to:

Oracle HTTP Server - Version 11.1.1.2.0 and later
Microsoft Windows x64 (64-bit)

Symptoms

After applying Microsoft Security patch Oracle HTTP Server startup failed with error in ohs1.log

[2018-07-19T10:06:37.2244-04:00] [OHS] [INCIDENT_ERROR:32] [OHS-9999] [core.c] [host_id: server1] [host_addr: 11.x.x.x] [pid: 21364] [tid: 540] [user: SYSTEM] [VirtualHost: main] (OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted.  :  make_sock: could not bind to address 0.0.0.0:8888

[2018-07-19T10:06:37.2244-04:00] [OHS] [INCIDENT_ERROR:20] [OHS-9999] [core.c] [host_id: server1] [host_addr: 11.x.x.x] [pid: 21364] [tid: 540] [user: SYSTEM] [VirtualHost: main]  no listening sockets available, shutting down

[2018-07-19T10:06:37.2244-04:00] [OHS] [ERROR:32] [OHS-9999] [core.c] [host_id: server1] [host_addr: 11.x.x.x] [pid: 21364] [tid: 540] [user: SYSTEM] [VirtualHost: main]  Unable to open logs

 

 

 

 

Changes

Issue reproduces after applying Microsoft July 2018 Security Patch KB4338824 

 

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.