FAQ | Search | Memberlist | Usergroups | Statistics | Profile | Log in to check your private messages | Log in | Register
Select Your Language
Infrastructure and management.
- Red Hat Enterprise Linux
- Red Hat Satellite
- Red Hat Subscription Management
- Red Hat Insights
- Red Hat Ansible Automation Platform
- Red Hat OpenShift
- Red Hat OpenStack Platform
- Red Hat OpenShift Container Platform
- Red Hat OpenShift Data Science
- Red Hat OpenShift Dedicated
- Red Hat Advanced Cluster Security for Kubernetes
- Red Hat Advanced Cluster Management for Kubernetes
- Red Hat Quay
- OpenShift Dev Spaces
- Red Hat OpenShift Service on AWS
- Red Hat Gluster Storage
- Red Hat Hyperconverged Infrastructure
- Red Hat Ceph Storage
- Red Hat OpenShift Data Foundation
- Red Hat Runtimes
- Red Hat JBoss Enterprise Application Platform
- Red Hat Data Grid
- Red Hat JBoss Web Server
- Red Hat Single Sign On
- Red Hat support for Spring Boot
- Red Hat build of Node.js
- Red Hat build of Quarkus
Integration and Automation
- Red Hat Application Foundations
- Red Hat Fuse
- Red Hat AMQ
- Red Hat 3scale API Management
httpd.service failed to start with an error "Cannot assign requested address: AH00072: make_sock: could not bind to address" during system boot
httpd.service fails to start during system boot when both of the following cases are satisfied: - httpd is configured to listen on a specific IP address in its configuration - NetworkManager.service is disabled
The following messages can be seen when attempting to start the httpd service during system boot:
- During boot systemd executes httpd.service before the network is completely up and running, which causes httpd to fail. This was reported in Fedora 17 as Bug 921566 - httpd does not wait for network start and fails. When it is going to be fixed in RHEL7?
Is there a fix available for https://bugzilla.redhat.com/show_bug.cgi?id=1352139 in RHEL7?
The issue occurs with IPv6 and it is not fixed by the newer package than systemd-219-42.el7.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
Current Customers and Partners
Log in for full access
New to Red Hat?
Learn more about Red Hat subscriptions
Using a Red Hat product through a public cloud?
How to access this content
Here are the common uses of Markdown.
Request a English Translation
Generating machine translation.
Apache – Cannot assign requested address: make_sock: could not bind to address
apache http webserver
Previously my IP was 10.0.6.63 , the apache server was working fine.
On reboot DHCP changed my IP address to 10.0.15.12 Now when i try to start apache it is giving me following error
Starting httpd: [Fri Jan 11 16:17:28 2013] [warn] module wsgi_module is already loaded, skipping (99)Cannot assign requested address: make_sock: could not bind to address 10.0.6.63:80 no listening sockets available, shutting down Unable to open logs
If you are working with a moving IP address do no use IP based virtualhosts but named based virtulahosts .
Check this apache documentation link
Linux – amazon ec2 – apache server restart issue.
I ran into this problem when I installed apache from source, but then tried to run
which was using a pre-installed version of apache. The stop directive in /etc/init.d/httpd was not removing the httpd.pid file that was created when starting the source-installed version of apache.
To determine if this is also the reason for your problem, find where the httpd.pid file is getting set when you run
If you installed from source and apache2 is living in /usr/local/apache2, then the httpd.pid file should get created in /usr/local/apache2/logs. When you stop apache by running
this file should get removed. So to test if the httpd.pid file is causing your problem, start apache by calling
and locate the httpd.pid file. Then try stopping apache by using
If the original httpd.pid file is still present, then that is why apache is unable to start when you use
To get my /etc/init.d/httpd file to work correctly, I explicitly put the call to apachectl in the start and stop methods:
Apache – Starting apache fails (could not bind to address 0.0.0.0:80)
Worked for me running this command:
OHS 12c Does Not Start With The Error: "Cannot assign requested address: make_sock: could not bind to address" (Doc ID 2001771.1)
Last updated on MAY 01, 2023
When trying to start Oracle HTTP server (OHS), the OHS does not start and the following errors are reported in the logs:
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.