Ok, you simply have a runaway process listening on port 443 (which is the port for HTTPS / SSL)
just run "lsof -i | grep 443" (I'm lazy I know there are better options for lsof) You will then see what process is listening on 443. Then decide if/how it should be shutdown to allow apache to start cleanly. (Using "kill -9" as the last resort) Martin On 9/21/06, Voytek Eymont <[EMAIL PROTECTED]> wrote:
On Thu, September 21, 2006 10:34 am, Martin Visser wrote: > Voytek, > > > You need to find the apache specific log file. It might be in > /var/log/apache. (The apache configuration files specify where logs are > written Martin, I have: ScoreBoardFile logs/apache_runtime_status CustomLog logs/mod_gzip.log common_with_mod_gzip_info2 ErrorLog "|/usr/sbin/cronolog /etc/httpd/logs/error/%d-error.log" CustomLog "|/usr/sbin/cronolog /etc/httpd/logs/%Y-%m-%d-access.log" combined ErrorLog logs/error_log TransferLog logs/access_log CustomLog logs/ssl_request_log \ hmmmm, I think maybe this is the one: # grep crit 21-error.log [Thu Sep 21 07:52:10 2006] [crit] (98)Address already in use: make_sock: could not bind to port 443 [Thu Sep 21 07:52:44 2006] [crit] (98)Address already in use: make_sock: could not bind to port 443 [Thu Sep 21 07:54:26 2006] [crit] (98)Address already in use: make_sock: could not bind to port 443 that's probably it..? how to overcome it ? -- Voytek -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
-- Regards, Martin Martin Visser -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
