I just did a new install of Webserve 1.2.10 on WXP home SP2. The install went over with no trouble. I configued the server with my domain and I configured MySQL, then I rebooted.
I assuemed that Apache2 would start automatically, but it didn't so I went to the start menu, and found webserv->Apache->apache start and it errored out with No installed service named "Apache2"
There's also no httpd log file.
Please advise.
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, I found the section Using Apache with Microsoft Windows and it says (in "Running Apache as a Service") to issue:
apache -k install
Which returns the error:
C:\WebServ\apache2\bin>Apache.exe -k install
(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:80
no listening sockets available, shutting down
Unable to open logs
Is there a way to find out if there is another server using this port?
I don't have any other http servers running, but I have on occasion run the development server for MS Web Developer Studio 2005 Express edition. I wonder if that's related.
Please advise.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well here an honest computer geek would say "just give up - if you can't figure that one out then you shouldn't be running a webserver" or "get linux stupid". But since I'm not a computer geek but just a person wanting to learn who's constantly been told those things when asking for help...
Check if you have something in XP, a firewall or something, that will so show you who's connecting to the internet and using which sockets. I'm using Windows 2000 so I have a freeware firewall called Outpost (www.agnitum.com) that continuously shows which programs and services are using which ports etc. If nothing else it's a great firewall program for you too.
Make sure it's not something silly like Skype using the port 80 and make sure you don't have stuff like SSI server stuff running to do with your MS Developer package...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do you know of a way to display which ports are used by which apps?
I was able to get Apache to start on port 90 (rather than port 80) but this only works around the problem.
Actually the problem is that I'm more of a Linux geek than Windows which is why I'm asking about this. I have the apache2, php and mysql running on a Debian system, which is a no-brainer. Oddly, on Windows I have less experience.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do you know of a way to display which ports are used by which apps?
I was able to get Apache to start on port 90 (rather than port 80) but this only works around the problem.
Actually the problem is that I'm more of a Linux geek than Windows which is why I'm asking about this. I have the apache2, php and mysql running on a Debian system, which is a no-brainer. Oddly, on Windows I have less experience.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Windows does not include the tools one takes for granted in unix systems and especially linux distros which are packed with everything you could possibly need for this kind of stuff. Until recently Windows didn't even include a firewall so don't be suprised if there's no way of seeing who's using which port.
I use the Outpost firewall not just as my software firewall but also as a way to control and see what windows is doing. A lot of hidden processes can be caught this way which are invisible to windows's usual process viewing applications. I recommend it. It will make your windows using life a lot easier.
If you don't want to try that then you have to consider something like Packetyzer or Ethereal. Note that they also require special drivers to be installed because windows does not have the necessary interfaces to see that kind of information off the NIC. Basically Windows's TCP/IP stack does not include many features and almost no useful programs to manage it.
I myself am in the other side of the fence trying to get there. I've got OpenSUSE 10 running on my laptop so that I can start slowly but surely moving to the linux world. Windows 2000 was the last 'usable' version of windows and now the only obstable for me moving to linux is Abode's application which I use a lot (yes there is Gimpshop but there is nothing similar to replace Illustrator). Also my HP NX6125 laptop isn't exactly the ideal platform for linux because of alot of hardware incompatiblities.
Actually now that you pushed me around a bit I managed to do a search on microsoft.com (yes, horrible isn't it!) and found this:
On Windows Server 2003 and on Windows XP-based computers, the service can log the following information:
• The ports that are used
• The processes that use the port
• Whether a process is a service
• The modules that a process loaded
• The user accounts that run a process
so there's a good hint for you when dealing with windows - there's actually a lot of useful bits of software on microsofts own site for this kind of stuff...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
..and if you aren't yet then let me tell you of my linux experience. First of all, back in the good old days when email was still done with pine and linux was all green and we were still using FreeBSD boxes at the ISP, I used to tinker with commandline and stuff (I only used X for the web and Gnome/KDE didn't exist), so don't assume I have antagonism towards unix in general, but I do have a problem with the linuxes of today...
Now, over a decade later, I appreciate that SUSE comes with a nice installer and it all recognises everything and everything seems to work. Then when you actually try to use it you are struck by some strange and questionable problems.
Both Gnome and KDE are full of nice easy admin interfaces for the newbie user like me to get started with. But do they work - hell no! After days of research I figure out they don't have permission to run 'su'. In fact even if I login as admin I don't have permission to run apps through su. How is a newbie supposed to start using the system if the first thing he has to do is sign up his user account and a bunch of apps via the command line to be part of the wheel (since none of the helpful graphical interfaces for this specific task DONT WORK). With this one simple 'feature' they have defeated the whole easy-to-install-and-get-started -idea of the distro. What a waste. And the KDE, when exiting it back to login screen, jumps to a completely incompatible screen resolution to my LCD - how is a newbie supposed to have any idea where to even start to look for a solution to a problem like that?
In the Linux world the newbie user is faced with a one hell-of-a chicken'n'egg problem. Linux has gotten a lot more complicated that the old unixes (my full install FBSD server was installed on a 500MB HD with plenty to spare) with a lot of automation and package management and all that.
Now i'm supposed to know things like 'you have to get the latest package for that driver' or 'or don't get the latest package for that before this package is updated' etc. I guess it all makes sense to the linux geeks but to a newbie it is meaningless and arbitrary. And what do you get when you go and ask about these things in the forums of irc: indignation: "why-would-you-want-do-that!", "read the MAN pages", "read the log files" etc. What if there are no MAN pages, what if I can't find a log file or the logging isn't turned on. In order to see the log files I have to turn debugin on somewhere. How? etc. etc.
This all reminds me of:
"All the planning charts and demolition orders have been on display in your local planning department on Alpha Centauri for fifty of your Earth years, so you've had plenty of time to lodge any formal complaint and it's far too late to start making a fuss about it now." ... "What do you mean you've never been to Alpha Centauri? For heaven's sake mankind, it's only four light years away you know. I'm sorry, but if you can't be bothered to take an interest in local affairs that's your own lookout." - Protstetnic Vogon Jeltz
Anyway, so I guess as a Web developer you are looking to get SSL working on that Apache too? Good luck. I've fought with it for days now and the mossl.org documentation is no help nor are the log files (because there aren't any!). So tell me when you get to it so we can figure it out together.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just did a new install of Webserve 1.2.10 on WXP home SP2. The install went over with no trouble. I configued the server with my domain and I configured MySQL, then I rebooted.
I assuemed that Apache2 would start automatically, but it didn't so I went to the start menu, and found webserv->Apache->apache start and it errored out with No installed service named "Apache2"
There's also no httpd log file.
Please advise.
Thanks.
I also assumed the same (on a W2K machine) but it doesn't! Just installing WebServ is nothing yet - you have to do some commandline stuff still...
See \apache2\httpd-docs-2.0.55.en.chm for chapter "Using Apache with Microsoft Windows"
in practice I did:
apache -k install
and then
apache -k start
Ok, I found the section Using Apache with Microsoft Windows and it says (in "Running Apache as a Service") to issue:
apache -k install
Which returns the error:
C:\WebServ\apache2\bin>Apache.exe -k install
(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:80
no listening sockets available, shutting down
Unable to open logs
Is there a way to find out if there is another server using this port?
I don't have any other http servers running, but I have on occasion run the development server for MS Web Developer Studio 2005 Express edition. I wonder if that's related.
Please advise.
Well here an honest computer geek would say "just give up - if you can't figure that one out then you shouldn't be running a webserver" or "get linux stupid". But since I'm not a computer geek but just a person wanting to learn who's constantly been told those things when asking for help...
Check if you have something in XP, a firewall or something, that will so show you who's connecting to the internet and using which sockets. I'm using Windows 2000 so I have a freeware firewall called Outpost (www.agnitum.com) that continuously shows which programs and services are using which ports etc. If nothing else it's a great firewall program for you too.
Make sure it's not something silly like Skype using the port 80 and make sure you don't have stuff like SSI server stuff running to do with your MS Developer package...
I'm not sure whether to be offended or not ;)
Do you know of a way to display which ports are used by which apps?
I was able to get Apache to start on port 90 (rather than port 80) but this only works around the problem.
Actually the problem is that I'm more of a Linux geek than Windows which is why I'm asking about this. I have the apache2, php and mysql running on a Debian system, which is a no-brainer. Oddly, on Windows I have less experience.
I'm not sure whether to be offended or not ;)
Do you know of a way to display which ports are used by which apps?
I was able to get Apache to start on port 90 (rather than port 80) but this only works around the problem.
Actually the problem is that I'm more of a Linux geek than Windows which is why I'm asking about this. I have the apache2, php and mysql running on a Debian system, which is a no-brainer. Oddly, on Windows I have less experience.
Windows does not include the tools one takes for granted in unix systems and especially linux distros which are packed with everything you could possibly need for this kind of stuff. Until recently Windows didn't even include a firewall so don't be suprised if there's no way of seeing who's using which port.
I use the Outpost firewall not just as my software firewall but also as a way to control and see what windows is doing. A lot of hidden processes can be caught this way which are invisible to windows's usual process viewing applications. I recommend it. It will make your windows using life a lot easier.
If you don't want to try that then you have to consider something like Packetyzer or Ethereal. Note that they also require special drivers to be installed because windows does not have the necessary interfaces to see that kind of information off the NIC. Basically Windows's TCP/IP stack does not include many features and almost no useful programs to manage it.
I myself am in the other side of the fence trying to get there. I've got OpenSUSE 10 running on my laptop so that I can start slowly but surely moving to the linux world. Windows 2000 was the last 'usable' version of windows and now the only obstable for me moving to linux is Abode's application which I use a lot (yes there is Gimpshop but there is nothing similar to replace Illustrator). Also my HP NX6125 laptop isn't exactly the ideal platform for linux because of alot of hardware incompatiblities.
Actually now that you pushed me around a bit I managed to do a search on microsoft.com (yes, horrible isn't it!) and found this:
Port Reporter tool
http://support.microsoft.com/kb/837243/en-us
On Windows Server 2003 and on Windows XP-based computers, the service can log the following information:
• The ports that are used
• The processes that use the port
• Whether a process is a service
• The modules that a process loaded
• The user accounts that run a process
so there's a good hint for you when dealing with windows - there's actually a lot of useful bits of software on microsofts own site for this kind of stuff...
And yes as a linux geek you should be offended :)
..and if you aren't yet then let me tell you of my linux experience. First of all, back in the good old days when email was still done with pine and linux was all green and we were still using FreeBSD boxes at the ISP, I used to tinker with commandline and stuff (I only used X for the web and Gnome/KDE didn't exist), so don't assume I have antagonism towards unix in general, but I do have a problem with the linuxes of today...
Now, over a decade later, I appreciate that SUSE comes with a nice installer and it all recognises everything and everything seems to work. Then when you actually try to use it you are struck by some strange and questionable problems.
Both Gnome and KDE are full of nice easy admin interfaces for the newbie user like me to get started with. But do they work - hell no! After days of research I figure out they don't have permission to run 'su'. In fact even if I login as admin I don't have permission to run apps through su. How is a newbie supposed to start using the system if the first thing he has to do is sign up his user account and a bunch of apps via the command line to be part of the wheel (since none of the helpful graphical interfaces for this specific task DONT WORK). With this one simple 'feature' they have defeated the whole easy-to-install-and-get-started -idea of the distro. What a waste. And the KDE, when exiting it back to login screen, jumps to a completely incompatible screen resolution to my LCD - how is a newbie supposed to have any idea where to even start to look for a solution to a problem like that?
In the Linux world the newbie user is faced with a one hell-of-a chicken'n'egg problem. Linux has gotten a lot more complicated that the old unixes (my full install FBSD server was installed on a 500MB HD with plenty to spare) with a lot of automation and package management and all that.
Now i'm supposed to know things like 'you have to get the latest package for that driver' or 'or don't get the latest package for that before this package is updated' etc. I guess it all makes sense to the linux geeks but to a newbie it is meaningless and arbitrary. And what do you get when you go and ask about these things in the forums of irc: indignation: "why-would-you-want-do-that!", "read the MAN pages", "read the log files" etc. What if there are no MAN pages, what if I can't find a log file or the logging isn't turned on. In order to see the log files I have to turn debugin on somewhere. How? etc. etc.
This all reminds me of:
"All the planning charts and demolition orders have been on display in your local planning department on Alpha Centauri for fifty of your Earth years, so you've had plenty of time to lodge any formal complaint and it's far too late to start making a fuss about it now." ... "What do you mean you've never been to Alpha Centauri? For heaven's sake mankind, it's only four light years away you know. I'm sorry, but if you can't be bothered to take an interest in local affairs that's your own lookout." - Protstetnic Vogon Jeltz
Anyway, so I guess as a Web developer you are looking to get SSL working on that Apache too? Good luck. I've fought with it for days now and the mossl.org documentation is no help nor are the log files (because there aren't any!). So tell me when you get to it so we can figure it out together.