Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Apache webserver error on startup [closed]

Tags:

apache

I just switch to Apache webserver and I receive an error

(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address 0.0.0.0:443 no listening sockets available, shutting down Unable to open logs

That is what I have got after running httpd from commandline. I reset my apache documentRoot as well as server's listening port to one that is free to use already, I have no idea about this error with port 443, is it something about SSL ?

UPDATE
I am using XP

like image 383
Mackintoast Avatar asked Feb 11 '12 15:02

Mackintoast


People also ask

Why is my Apache Web server not working?

There are several reasons your Apache server might fail to run. Something could be blocking the port it uses; there could be another instance of Apache already running; or there might be an incompatibility with the version of PHP you're using in MAMP.


2 Answers

For Windows XP

netstat -ano 

Find the process id that is using port 443, and kill it using task manager

For me it was IIS using the port.

like image 67
keith Avatar answered Nov 11 '22 16:11

keith


Copying and pasting your exact error into google gave a couple of answers:

  • https://wiki.apache.org/httpd/CouldNotBindToAddress

Port 443 seems to already be in use. Possibly by your old server. One of the three covered errors in the official apache wiki above is:

Address is already in use

Something else is already using the port in question.

Run one of the following commands to check if a running process is holding the port needed by apache open.

On Linux/Unix run $>  netstat -plant $> # or $> sudo lsof -i:80  On Windows run $>  netstat -ano  On Mac OS X / FreeBSD run $> netstat -Wan |grep 80 $> # or, to get the pid $> sudo lsof -i:80 

Once you see these results, you can choose to kill the program in question, or change the port that Apache uses.

If Apache (httpd, apache2, etc) is the application listening on these ports, but you can't stop it using your normal procedure, someone may have deleted the servers PidFile. The PidFile records the process ID of the parent process and is how most scripts test to see if Apache is running. You can manually stop the server by determining the PID of the parent process and sending it a SIGTERM.

like image 23
dm03514 Avatar answered Nov 11 '22 16:11

dm03514