Comments on: Apache HTTPD: Address already in use: make_sock: could not bind to address 0.0.0.0:443 http://www.digitalsanctum.com/2007/08/18/apache-httpd-address-already-in-use-make_sock-could-not-bind-to-address-0000443/ software development, technology and other square topics Sat, 22 Nov 2008 08:24:28 +0000 http://wordpress.org/?v=2.6.1 By: Jenny http://www.digitalsanctum.com/2007/08/18/apache-httpd-address-already-in-use-make_sock-could-not-bind-to-address-0000443/#comment-7118 Jenny Thu, 03 Apr 2008 04:03:56 +0000 http://www.digitalsanctum.com/2007/08/18/apache-httpd-address-already-in-use-make_sock-could-not-bind-to-address-0000443/#comment-7118 Thank you. Thank you.

]]> By: Aran http://www.digitalsanctum.com/2007/08/18/apache-httpd-address-already-in-use-make_sock-could-not-bind-to-address-0000443/#comment-5266 Aran Mon, 03 Dec 2007 16:20:31 +0000 http://www.digitalsanctum.com/2007/08/18/apache-httpd-address-already-in-use-make_sock-could-not-bind-to-address-0000443/#comment-5266 Thanks. This worked perfectly for me on a Suse 10 install running Apache 2. In my case the processes were running as wwwrun, but same difference. I just killed all the processes running as wwwrun, and was able to then do a rcapache2 restart with success. Thanks. This worked perfectly for me on a Suse 10 install running Apache 2. In my case the processes were running as wwwrun, but same difference. I just killed all the processes running as wwwrun, and was able to then do a rcapache2 restart with success.

]]> By: Pid http://www.digitalsanctum.com/2007/08/18/apache-httpd-address-already-in-use-make_sock-could-not-bind-to-address-0000443/#comment-3759 Pid Wed, 22 Aug 2007 10:53:06 +0000 http://www.digitalsanctum.com/2007/08/18/apache-httpd-address-already-in-use-make_sock-could-not-bind-to-address-0000443/#comment-3759 Yes, yesterday. Entirely coincidentally as I was originally reading your 20 tomcat tips. I did exactly the same thing as you to kill the process. No idea what caused it, as I killed the process before inspecting it further. It was on a server with Plesk though, which was having trouble executing an upgrade. Yes, yesterday. Entirely coincidentally as I was originally reading your 20 tomcat tips.
I did exactly the same thing as you to kill the process.

No idea what caused it, as I killed the process before inspecting it further.

It was on a server with Plesk though, which was having trouble executing an upgrade.

]]>