My Oracle Support Banner

OracleAS OHS Fails to Start - "Permission denied: make_sock: could not bind to port" After LOHA Backup Restored (Doc ID 754486.1)

Last updated on JULY 01, 2024

Applies to:

Oracle HTTP Server - Version 10.1.3.1.0 and later
Oracle Fusion Middleware - Version 10.1.3.1.0 and later
Generic UNIX

Symptoms

OracleAS 10g HTTP Server on a Unix platform,  has been configured to listen on a port or ports with value < 1024

A startup of HTTP Server is failing.

The OPMN  HTTP_Server~1.log shows no error, only

--------
<date time> Start process
--------

The OHS error_log shows an error

.. [crit] (13)Permission denied: make_sock: could not bind to port ...

Analysis of the output from

suggests there are no other processes locking the port / socket required by HTTP Server.

Changes

Oracle HTTP Server was working fine, but problem elsewhere in the technology stack necessitated a restore from backup - LOHA -  using the OracleAS Backup Recovery Manager i.e the bkp_restore script. Following the restore, HTTP Server no longer starts.

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.