Apache Error Address Already In Use Make_sock
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 how to make a sock bun already in use: make_sock: could not bind to address 0.0.0.0:80 on how to make a sock snowman Ubuntu [SOLVED] Category: Common Fixes, Technical Support Pre-Flight Check These instructions are intended specifically for solving the make sock dolls 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 make sock monkey 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
Make Ipod Sock
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 proce
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad
How To Make A Sock Puppet
Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter how to make a sock elephant Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read how to make a sock animal before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support Desktop Environments [SOLVED] (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 Having an Issue With https://www.liquidweb.com/kb/error-98address-already-in-use-make_sock-could-not-bind-to-address-0-0-0-080-on-ubuntu-solved/ Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Results 1 to 9 of 9 Thread: (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode December 3rd, 2010 #1 https://ubuntuforums.org/showthread.php?t=1636667 hhabashy View Profile View Forum Posts Private Message First Cup of Ubuntu Join Date Nov 2007 Beans 3 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 I would like to state first of all I am a novice with Linux, but have working in IT for 15 years. I have been searching the web on this issue for almost 2 days (off and on), and have found that my particular issue was not the same as the norm for this particular error code. I would like to give back (if you will). Apparently having a cert.key password protected will hang Apache2 (maybe Apache as well). The solution was to remove the password on the cert.key and that solved my problem. The general consensus with resolving this issue did help me figure out that apache2 was running but waiting for password on boot-up. The following command which you will find everywhere out in the cloud is as follows: sudo netstat -ltnp | grep ':80' (it is important to note that apache was hanging and it did not matter what port I decided to investigate) This would return the following: tcp
due to ports 80 and 443 magically being in-use...why? General support questions including new installations Post Reply Print view Search Advanced search 14 posts 1 2 Next torontob123 Posts: 95 Joined: 2009/11/30 20:21:14 http://www.centos.org/forums/viewtopic.php?t=14681 httpd can't start due to ports 80 and 443 magically being in-use...why? Quote Postby torontob123 » 2009/12/04 01:28:22 Hi Guys,Recently I installed an SSL certificate from GoDaddy on my Amazon EC2 instance which runs CentOS 5. All has been good till I installed the SSL certificate. Everytime I restart the system it fails to have httpd service working because:[root@ip-]# service httpd startStarting httpd: (98)Address already in use: make_sock: could how to not bind to address 0.0.0.0:80no listening sockets available, shutting downUnable to open logsI looked on the net and found a solution which says I should change port 80 and port 443 in files httpd.conf and ssl.conf to port 88 and 553 and restart apache, change back the ports to 80 and 443 and restart again. This method worked before but now I am stuck with it not starting with ports how to make 80 and 443 and if I change these ports then I can't reach my site and I have to add port number wtih : which is really not good.1- What causes this problem and where can I look to debug it?2- What can I do to permenently stop this problem? is there any place that I can dedicate these two ports to apache user?Thanks a bunch Top michaelnel Posts: 1478 Joined: 2006/05/29 16:50:11 Location: San Francisco, CA httpd can't start due to ports 80 and 443 magically being in Quote Postby michaelnel » 2009/12/04 18:40:28 I would use the "fuser" command to find out what is using ports 80 and 443, then proceed from there.Code: Select all# fuser 80/tcp
80/tcp: 2850 12763 15537 18030 30044 32226
The return from fuser shows that processes with pids 2850 12763 15537 18030 30044 32226 are using port 80.Code: Select all# ps aux | grep 2850 | grep -v grep
root 2850 0.0 0.4 318772 30428 ? Ssl Oct22 0:03 /usr/sbin/httpd
So, in this case it is httpd process listening on port 80. Look for children:Code: Select all# pgrep httpd
2850
12763
15537
18030
30044
32226
So those are