Starting Oracle HTTP Server Fails With” Permission denied: AH00072: make_sock: could not bind to address xx.xx.xx.xx:443″

Starting Oracle HTTP Server Fails With” Permission denied: AH00072: make_sock: could not bind to address xx.xx.xx.xx:443″
Post upgradation they are unable to bring up the OHS for port 80 and can see Permission denied: AH00072: make_sock: could not bind to address xx.xx.xx.xx:80

<2018-01-19 07:22:27> <INFO> <OHS-0> <(13)Permission denied: AH00072: make_sock: could not bind to address xx.xx.xx.xx:443>
<2018-01-19 07:22:27> <INFO> <OHS-0> <no listening sockets available, shutting down>
<2018-01-19 07:22:27> <INFO> <OHS-0> <AH00015: Unable to open logs>
<2018-01-19 07:22:27> <INFO> <OHS-0> <<PATH TO ORACLE_HOME>/../ohs/bin/launch httpd -DOHS_MPM_EVENT -d <PATH TO DOMAIN_HOME>/config/fmwconfig/components/OHS/instances/ohs1 -k start -f <PATH TO DOMAIN_HOME>/config/fmwconfig/components/OHS/instances/ohs1/httpd.conf: exit status = 1>
<2018-01-19 07:22:27> <INFO> <OHS-4005> <Check the instance log file for more information: <PATH TO DOMAIN_HOME>/servers/ohs1/logs/ohs1.log>
<2018-01-19 07:22:27> <SEVERE> <OHS-0> <Failed to start the server ohs1>

On a UNIX system, TCP ports in a reserved range (typically less than 1024) can only be bound by processes with root privilege. Oracle HTTP Server always runs as a non-root user; that is, the user who installed Oracle Fusion Middleware. On UNIX, special configuration required to allow Oracle HTTP Server to bind to privileged ports were missing.

Without root privilege OHS will not be able to bind to TCP ports in a reserved range (typically less than 1024)

Update the ORACLE_HOME/ohs/bin/launch file by performing the following steps as the super user (if you do not have access to super user privileges, have your system administrator perform these steps):

  1. Change ownership of the file to root:
    chown root $ORACLE_HOME/ohs/bin/launch
  2. Change the permissions on the file as follows:
    chmod 4750 $ORACLE_HOME/ohs/bin/launch
  3. Configure the User and Group directive in httpd.conf.
    -The user ID for User should be the same user ID that created the instance. The group ID for Group must be the same group ID used to create the instance.

User and Group directive should be updated with same id and group that will used to start it

https://docs.oracle.com/middleware/12213/webtier/administer-ohs/getstart.htm#HSADM852

Refer above link for more detrails .

Related Posts

Leave a Reply

Your email address will not be published.