Starting Oracle HTTP Server Failed With" Permission denied: AH00072: make_sock: could not bind to address xx.xx.xx.xx:443"

(Doc ID 2350791.1)

Last updated on JANUARY 19, 2018

Applies to:

Oracle HTTP Server - Version and later
Information in this document applies to any platform.
The note applies to non-Windows platforms only


Oracle HTTP Server start fail with error recorded in ohs_nm.log

<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> </u01/app/oracle/wlserver/../ohs/bin/launch httpd -DOHS_MPM_EVENT -d /u01/app/oracle/user_projects/domains/ohs/config/fmwconfig/components/OHS/instances/ohs1 -k start -f /u01/app/oracle/user_projects/domains/ohs/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: /u01/app/oracle/user_projects/domains/ohs/servers/ohs1/logs/ohs1.log>
<2018-01-19 07:22:27> <SEVERE> <OHS-0> <Failed to start the server ohs1>



Issue occur after changing ownership of all files under $ORACLE_HOME to oracle user (eg. oracle) using chown command. 


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 hundreds of Community platforms