Error Address Already In Use 98
Contents |
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
Dev Log Address Already In Use
Fixes, Technical Support Pre-Flight Check These instructions are intended specifically for solving the error: error binding socket addr af_inet (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 error errno 98 address already in use 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
Linux Error 98 Address Already In Use
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
Shadowsocks Socket Error Errno 98 Address Already In Use
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 14.04 LTS Post navigation ←Error: /usr/sbin/ifconfig: No such file or directory [SOLVED]How to Install Log
here for a quick overview of the site Help Center Detailed answers to any questions you might 98 address already in use make_sock could not bind to address 443 have Meta Discuss the workings and policies of this site About
98 Address Already In Use Nginx
Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads apache2 98 address already in use with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million https://www.liquidweb.com/kb/error-98address-already-in-use-make_sock-could-not-bind-to-address-0-0-0-080-on-ubuntu-solved/ programmers, just like you, helping each other. Join them; it only takes a minute: Sign up python socket.error: [Errno 98] Address already in use [closed] up vote 12 down vote favorite 2 when i setup application.py, it shows that socket.error: [Errno 98] Address already in use. Traceback (most recent call last): File "application.py", line 121, in http://stackoverflow.com/questions/17780291/python-socket-error-errno-98-address-already-in-use
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 http://askubuntu.com/questions/277162/apache-fails-to-start-address-already-in-use-but-not-really workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring 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: address already Anybody can ask a question Anybody can answer The 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. address already in I get this error: (98) Address already in use: make_sock: could not bind to 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/apa