Apache Binding Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and
Make_sock Could Not Bind To Address No Listening Sockets Available
policies of this site About Us Learn more about Stack Overflow the apache could not bind to address 0.0.0.0 80 windows company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags
Make_sock: Could Not Bind To Address [::]:443
Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes make_sock: could not bind to address no listening sockets available, shutting down a minute: Sign up Starting apache fails (could not bind to address 0.0.0.0:80) up vote 34 down vote favorite 26 Update: Already fixed, it seems that one of VirtualHosts configurations files was wrong in sites-enabled. I have Ubuntu 11.10 When I run the command to start apache2: sudo /etc/init.d/apache2 start I get the following error message: Starting web server apache2 apache2: (13)permission denied: make_sock Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs Action 'start' failed. I run this command in order to get the process that is using the port 80: sudo netstat -ltnp | grep ':80' Which returns this output: tcp6 0 0 :::80 :::* LISTEN 1176/ To know which process is I run this command: ps -wlp1176 That returns: F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD 5 D 33 1176 1 0 80 0 - 0 exit ? 00:00:00 apache2 But if I try to kill the process: sudo kill -9 1176 It doesn't kill it, if I run again the netstat command still appears listening and apache start fails. Any suggestions? apache port kill netstat share|improve this question edited Apr 15 '12 at 8:17 asked Apr 15 '12 at 7:39 rfc1484 2,520103565 2 So what is pid 1176? (ps -wlp1176) –geekosaur Apr 15 '12 at 7:43
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this
Ah00072: Make_sock: Could Not Bind To Address [::]:80
site About Us Learn more about Stack Overflow the company Business Learn more cannot assign requested address: make_sock: could not bind to address about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu
Fuser -k -n Tcp 80
is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The http://stackoverflow.com/questions/10160339/starting-apache-fails-could-not-bind-to-address-0-0-0-080 best answers are voted up and rise to the top Apache fails to start, Address already in use (but not really) up vote 23 down vote favorite 7 I'm trying to set up a VM running Ubuntu 12.04. I have two virtual hosts configured using port 80, but Apache will not start. I get this error: (98) Address already in use: make_sock: could not bind to http://askubuntu.com/questions/277162/apache-fails-to-start-address-already-in-use-but-not-really address 0.0.0.0:80 The output of netstat -tulpn shows that nothing is using port 80. What could possibly be causing this? 12.04 apache2 vm share|improve this question asked Apr 2 '13 at 14:59 Gunner Barnes 124117 are you starting it as root? By default only root can open ports below 1024. –onse Apr 2 '13 at 15:02 Yes, I am. It was running at one point when I had just one virtual host configured, so I've since removed the other virtual host to try to remedy the issue, but no luck with that either. –Gunner Barnes Apr 2 '13 at 15:15 Does you host have something running on port 80 and you're in bridged mode for the guest? I don't know that it would do that, but it seems probable –RobotHumans Apr 2 '13 at 15:41 Have you tried the suggestions from Starting apache fails (could not bind to address 0.0.0.0:80)? And please also include the output of grep -ri listen /etc/apache and sudo netstat -ntlp | grep 80. –gertvdijk Apr 2 '13 at 19:57 1 grep -ri listen /etc/apache2 outputs: etc/apache2/httpd.conf: Listen 80 /etc/apache2/httpd.conf: Listen 443 /etc/apa
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About http://askubuntu.com/questions/338218/why-am-i-getting-permission-denied-make-sock-could-not-bind-to-address-when Us Learn more about Stack Overflow the company Business Learn more about hiring https://www.liquidweb.com/kb/error-98address-already-in-use-make_sock-could-not-bind-to-address-0-0-0-080-on-ubuntu-solved/ developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted could not up and rise to the top Why am I getting “Permission denied: make_sock: could not bind to address” when starting Apache2? up vote 14 down vote favorite 10 I can stop it using /etc/init.d/apache2 stop But when I want to start it again using: /etc/init.d/apache2 start I get this error: Starting web server apache2 /usr/sbin/apache2ctl: 87: ulimit: error setting limit (Operation not permitted) apache2: Could not reliably determine could not bind the server's fully qualified domain name, using 127.0.1.1 for ServerName (13)Permission denied: make_sock: could not bind to address [::]:80 (13)Permission denied: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logs Action 'start' failed. The Apache error log may have more information. [fail] server permissions apache2 share|improve this question edited Aug 28 '13 at 7:12 Andrea Corbellini 8,89713054 asked Aug 28 '13 at 5:43 Artisan 2441412 add a comment| 4 Answers 4 active oldest votes up vote 25 down vote accepted Some words about the errors you get which hopefully will save you from similar situations in future. In Linux ports from 0 to 1024 are reserved for system use. This means that in order to use one, you must have the authority to change - access basic system settings. The root user has such privileges and can actually use a port from the range 0 - 1024. In your problem as you can see, the system through Apache2 response indicates the root of the problem ([...]could not bind to address blah blah 80): (13)Permission denied: make_sock: could not bind to address [::]:80 (13)Permission denied: make_sock: could not bind to address 0.0.0.0:80 When the Apach
Getting Started Home Page | Knowledge Base 24 X 7 HEROIC SUPPORT 800.580.4985 (1-517-322-0434) Find Answers To Web Hosting Questions SearchSearch Error: (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 on Ubuntu [SOLVED] Category: Common Fixes, Technical Support Pre-Flight Check These instructions are intended specifically for solving the error: (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 I’ll be working from both Liquid Web Core Managed Ubuntu 12.04 LTS and 14.04 LTS servers, and I'll be logged in as root. Option #1: Multiple ‘Listen' Directive Entries in Configuration Files In some cases the (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 error could be caused by multiple Listen directives attempting to bond to the same port (port 80 in this case). We'll take a look at the configuration files to verify whether or not this may be the case. For both Ubuntu 12.04 LTS and Ubuntu 14.04 LTS search the following configuration file: grep Listen /etc/apache2/ports.conf which for my search resulted in: Listen 80 Listen 81 Listen 80 Listen 443 Listen 443 It looks like there are two Listen directives for port 80 and port 443, but we're only concerned about port 80, per the error we received (0.0.0.0:80). Edit the file, and correct the duplicate Listen directive. For a refresher on editing files with vim see: New User Tutorial: Overview of the Vim Text Editor vim /etc/apache2/ports.conf Option #2: Another Process is Already Using Port 80 Evaluate which process(es) may be using port 80 with the following: Use: fuser -n tcp 80 in combination with: ps aux | grep PID (with PID equal to the ports listed with the fuser command) to evaluate which process is associated with the PIDs using port 80. Or, use the following one-liner: ss -plnt sport eq :80 Then, kill of the offending process(es). Want to Try This Tutorial? Launch a Free* Storm Server *For new customers only Email Get Started Now Thank you. Your request has been submitted and we’ll be sending you a $75 Storm coupon shortly! Be Sociable, Share! Tweet Related ArticlesError: /usr/sbin/ifconfig: No such file or directory [SOLVED]How to List Which Apache Modules are Enabled on UbuntuHow to Install lsyncd on Ubuntu 14.04 LTSHow To List and Attach to Docker ContainersHow to Install Logwatch on Ubuntu 1