httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Liron Newman <plast...@ultinet.org>
Subject [users@httpd] Re: Apache not listening after restart from Apache Monitor (Win32)
Date Mon, 23 Feb 2004 03:12:37 GMT
Hello again,

I am reposting this message because I saw the list is active but I got 
no reply. I am aware that this is usually frowned upon but this is a 
very big issue (IMHO) and I would greatly appreciate it if anyone would 
be able to direct me to a webpage, an open bug in bugzilla, or any kind 
of resource that will help me tackle the problem. I /have/ searched the 
web and Apache's bugzilla, and this list's archive, but found no 
solution. For lack of a better word - I am kinda desperate. :)

Even your guesses are welcome.

As for the repost thing - Please direct all rotten tomatoes to /dev/null. :)

Liron Newman wrote:

> Hello everyone,
>
> Recently, my Apache server (2.0.48, Win2k Pro SP4 with all patches, 
> runs as service, listening on all IPs, a few vhosts, PHP 4.3.4) 
> started acting up when I choose to restart it via the Apache Monitor 
> on my system tray. Instead of simply restarting, what happens is that 
> the server seemingly reloads, but when I attempt to connect to it my 
> browser fails. After I restart the _service_ the server works great.
>
> A few notes:
> 1. When telnetting to the server after the monitor-restart the server 
> *does* answer, but when I type GET /<CR> absolutely nothing happens. 
> Naturally, after restarting the _service_ a GET / via telnet gives my 
> my main vhost's index page.
> 2. This wouldn't have bothered me so much if it wasn't for this: If 
> for some reason a child process dies, Apache starts a new child 
> process, an action that results with the same defective situation. For 
> obvious reasons this is very disturbing.
> 3. This wasn't like this from the start. The problem is I can't put my 
> finger on when it started or what changed about the server before it 
> started. I know finding the changed element in the system is the key 
> to any mystery-problem. :)
>
> The temporary "solution" I use now is a script that tests the server's 
> response with GNU Wget every 30 minutes and runs "net stop apache2" 
> and "net start apache2" if Wget fails. Obviously this isn't a 
> solution... :)
>
> Any ideas? I searched the net but couldn't find anything.. I'm stomped.
>
> Thanks in advance. :)
>
> My error.log (on loglevel info):
> [Sat Feb 21 03:14:28 2004] [notice] Parent: Created child process 6152
> [Sat Feb 21 03:14:28 2004] [notice] Child 6152: Child process is running
> [Sat Feb 21 03:14:28 2004] [info] Parent: Duplicating socket 280 and 
> sending it to child process 6152
> [Sat Feb 21 03:14:28 2004] [notice] Child 6152: Acquired the start mutex.
> [Sat Feb 21 03:14:28 2004] [notice] Child 6152: Starting 250 worker 
> threads.
> [Sat Feb 21 03:14:53 2004] [warn] (OS 64)The specified network name is 
> no longer available.  : winnt_accept: Asynchronous AcceptEx failed.
> [Sat Feb 21 03:15:11 2004] [notice] Parent: Received restart signal -- 
> Restarting the server.
> [Sat Feb 21 03:15:11 2004] [notice] Child 6152: Exit event signaled. 
> Child process is ending.
> [Sat Feb 21 03:15:11 2004] [warn] (OS 995)The I/O operation has been 
> aborted because of either a thread exit or an application request.  : 
> winnt_accept: Asynchronous AcceptEx failed.
> [Sat Feb 21 03:15:11 2004] [info] Child 6152: Accept thread exiting.
> [Sat Feb 21 03:15:11 2004] [notice] Parent: Created child process 3796
> [Sat Feb 21 03:15:11 2004] [notice] Child 3796: Child process is running
> [Sat Feb 21 03:15:11 2004] [info] Parent: Duplicating socket 280 and 
> sending it to child process 3796
> [Sat Feb 21 03:15:12 2004] [notice] Child 3796: Acquired the start mutex.
> [Sat Feb 21 03:15:12 2004] [notice] Child 6152: Released the start mutex
> [Sat Feb 21 03:15:12 2004] [notice] Child 3796: Starting 250 worker 
> threads.
> [Sat Feb 21 03:15:12 2004] [info] Child 6152: 250 threads blocked on 
> the completion port
> [Sat Feb 21 03:15:13 2004] [notice] Child 6152: Waiting for 250 worker 
> threads to exit.
> [Sat Feb 21 03:15:13 2004] [notice] Child 6152: All worker threads 
> have exited.
> [Sat Feb 21 03:15:13 2004] [notice] Child 6152: Child process is exiting
> [Sat Feb 21 03:16:03 2004] [notice] Parent: Received shutdown signal 
> -- Shutting down the server.
> [Sat Feb 21 03:16:03 2004] [notice] Child 3796: Exit event signaled. 
> Child process is ending.
> [Sat Feb 21 03:16:03 2004] [warn] (OS 995)The I/O operation has been 
> aborted because of either a thread exit or an application request.  : 
> winnt_accept: Asynchronous AcceptEx failed.
> [Sat Feb 21 03:16:03 2004] [info] Child 3796: Accept thread exiting.
> [Sat Feb 21 03:16:04 2004] [notice] Child 3796: Released the start mutex
> [Sat Feb 21 03:16:04 2004] [info] Child 3796: 250 threads blocked on 
> the completion port
> [Sat Feb 21 03:16:05 2004] [notice] Child 3796: Waiting for 250 worker 
> threads to exit.
> [Sat Feb 21 03:16:05 2004] [notice] Child 3796: All worker threads 
> have exited.
> [Sat Feb 21 03:16:05 2004] [notice] Child 3796: Child process is exiting
> [Sat Feb 21 03:16:05 2004] [notice] Parent: Child process exited 
> successfully.
>
>

---------------------------------------------------------------------
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