I do have appropriate permissions, as I have been able to stop it before. There is no error message being logged when I try to stop it.
I ran ps -A which listed all processes. httpd (apache) was not one of them. I am assuming PID means Port ID(?), and neither 443 nor 80 was listed... This is all very strange and I am starting to sense that I will have to reinstall Apache... -----Original Message----- From: Milt Epstein To: Tomcat Users List Sent: 12/15/2002 5:44 PM Subject: RE: Almost there...Updated Apach-Tomcat with mod_jk .. please he lp! On Sun, 15 Dec 2002, Denise Mangano wrote: > Sorry, I thought I posted the exact message I was getting. It says > "[Sun Dec 15 00:42:27 2002] [crit] (98)Address already in use: > make_sock: could not bind to port 443". I am trying to figure out > what else is listening to that port but with Tomcat uninstalled > there shouldn't be any other. Someone suggested multiple instances > of Apache running, but I do not know how to check this. When I try > to stop the httpd service it fails, and there is no entry in the > error_log... Run ps, from that you'll be able to tell if Apache is already running. You might need to check the man page to see what options you need to use. That you can't successfully stop the httpd service (i.e. apache) is an indication that that is the problem. What error message to you get when you try to stop it. Do you have the appropriate permissions to do that? > -----Original Message----- > From: micael > To: Tomcat Users List > Sent: 12/15/2002 3:59 PM > Subject: RE: Almost there...Updated Apach-Tomcat with mod_jk .. please he > lp! > > > > At 03:38 PM 12/15/2002 -0500, you wrote: > >Jake, > > > >Thanks for supplying me with that info. I will certainly refer to it, > when > >I set up Tomcat again. However, first I need to get Apache back up and > >running. I know this is slightly off topic, but can you tell me how to > >check what else is trying to access port 443. > > Not sure what you meant by "trying to access" but that would not be the > problem, if you mean that literally. Rather, the problem is that some > application is listening at port 443. You have something that is > listening > at port 443 for others to access. So, you should have a server set to > listen at 443. > > > Micael > > ------------------------------------------------------- > > This electronic mail transmission and any accompanying documents > contain > information belonging to the sender which may be confidential and > legally > privileged. This information is intended only for the use of the > individual or entity to whom this electronic mail transmission was sent > as > indicated above. If you are not the intended recipient, any disclosure, > copying, distribution, or action taken in reliance on the contents of > the > information contained in this transmission is strictly prohibited. If > you > have received this transmission in error, please delete the message. > Thank > you > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > Milt Epstein Research Programmer Integration and Software Engineering (ISE) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
