httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Boyle Owen" <Owen.Bo...@swx.com>
Subject RE: [users@httpd] reseting the apache server
Date Tue, 15 Jan 2008 07:38:55 GMT
> -----Original Message-----
> From: joshuav@gmail.com [mailto:joshuav@gmail.com] On Behalf 
> Of joshua vogelstein
> Sent: Tuesday, January 15, 2008 1:13 AM
> To: users@httpd.apache.org
> Subject: [users@httpd] reseting the apache server
> 
> sometimes i modify my httpd.conf file to try to add a 
> function (eg, file-serving).  however, this often results in 
> some kind of error, and the apache server will not restart.  
> problematically, even after commenting out the additional 
> lines of code, the apache server still refuses to start.  if 
> i reboot my computer, everything works fine again.  i am 
> using apache 2.0.61 and windows XP.  i'm using this old 
> version of apache because i was unable to get the new version 
> working with subversion and windows XP.  when trying to 
> restart (after the httpd.conf file is fixed) i receive the 
> following error: 
> 
> (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
> Note the errors or messages above, and press the <ESC> key to 
> exit.  21...
> 
> suggesting to me that the port is unavailable.  

Exactly. The port is still in use - presumably by the previous instance
of apache, which has not really died (Q: what happens if you now try to
hit the site? Does the request succeed? With the old config?)

It looks like your restart procedure is not stopping apache, even though
it is trying to start a new process. I don't know how it works on XP,
but on unix, a restart is quite different from a stop-start (restart =
SIGHUP, stop-start = SIGKILL then start). So maybe try the following:

1) Get apache running nad verify site is up with config A
2) Make obvious change to config (eg, new docroot - B)
3) do restart
4) when you get the error as above, hit the site again - what version do
you get (I bet A).
5) reboot etc to get back to 1) - now you should see version B.
6) switch config back to A
7) do a stop (not a restart)
8) is site up? (should not be - if it is, your stop process is bust)
9) do a start
10) what site do you get (should be A)

Rgds,
Owen Boyle
Disclaimer: Any disclaimer attached to this message may be ignored. 




>this is 
> incredibly annoying because i'm doing all this work remotely, 
> so i have to reboot my system remotely each time i screw 
> something up, which is quite often.  any body know a way around this? 
> 
> thanks, joshua
> 
>
 
 
This message is for the named person's use only. It may contain confidential, proprietary
or legally privileged information. If you receive this message in error, please notify the
sender urgently and then immediately delete the message and any copies of it from your system.
Please also immediately destroy any hardcopies of the message. The sender's company reserves
the right to monitor all e-mail communications through their networks.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message