IBM Support

Apache httpd fails to start resulting in "Address already in use: make_sock: could not bind to address" error

Troubleshooting


Problem

Attempts to start the Apache httpd service using IBM Cloud Orchestrator fails resulting in the error "Address already in use: make_sock: could not bind to address".

Symptom

The httpd service fails to start.

Example:

[root@central2 httpd]# service httpd start
Starting httpd: (98)Address already in use: make_sock: could not bind
to address [::]:443
(98)Address already in use: make_sock: could not bind to address
0.0.0.0:443
no listening sockets available, shutting down
Unable to open logs
[FAILED]

Cause

The operating system on central server 2 was recently updated (in this scenario to RHEL 6.7).
This impacted the Apache httpd configuration, very likely because RHEL 6.7 introduced a yum update for httpd.

Diagnosing The Problem

Check the yum history to see if any recent changes have been applied to your httpd package.

Check the error to see if the message indicates Port 443 is being used on CS2.

----->
Starting httpd: (98)Address already in use: make_sock: could not bind
to address [::]:443
make_sock: could not bind to address 0.0.0.0:443
<----

Apache http server refuses to start if Port 443 is overlapped by the ssl.conf file in /etc/httpd/conf.d/ folder.

Resolving The Problem

Procedure:

  1. Rename ssl.conf file to ssl.conf.bak
  2. Start httpd
[{"Product":{"code":"SS4KMC","label":"IBM SmartCloud Orchestrator"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"General Information","Platform":[{"code":"PF016","label":"Linux"}],"Version":"2.4;2.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

More support for:
IBM SmartCloud Orchestrator

Software version:
2.4, 2.5

Operating system(s):
Linux

Document number:
609193

Modified date:
17 June 2018

UID

swg2C1000052