Hi Voytek,
It means some process is using the 443 port.
You can try to figure out that process and either stop it
or change the port for that process.
Alternatively you can change apache configuration
and change ssl port from 443 to a different port and
try to start you application
vi httpd.conf
and replace the port 443 with 448. Now apache will
use port 448 for SSL.
restart apache and see if it starts.
HTH
Saurabh
Voytek Eymont 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 ?
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
