httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 48949] fcgid processes never get killed after gaceful restart
Date Tue, 24 Aug 2010 23:07:41 GMT

--- Comment #5 from Gregg L. Smith <> 2010-08-24 19:07:37 EDT ---
Confirmed on Windows XP

Long standing bug going back to Apache/2.2.8 and mod_fcgid/2.2. 
Has as bad of an effect on Windows just Apache's death is a little more sudden.

If you start at console, use php via mod_fcgid and then restart with a
ctrl+ScrLk, you get this;

Event Type:    Information
Event Source:    DrWatson

The application, H:\Apache23\bin\httpd.exe, generated an application error The
error occurred on 08/24/2010 @ 15:13:13.046 The exception generated was
c0000005 at address 46434CB2 (mod_fcgid!wakeup_thread)

Opening up Task Manager and looking in the processes you see a long httpd
process hanging around. It has a lock on port 80 and the logs so you see
nothing in the error log. Apache still is answering at this point but shows
stopped and has released the console.

If Apache is running as a service on your production server, and you restart
the service you see this in rapid succession in the event log in order of

The Apache service named reported 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 .

The Apache service named reported the following error:
>>> no listening sockets available, shutting down .

The Apache service named reported the following error:
>>> Unable to open logs

Apples and Oranges to some degree since the first event log is running Apache
2.3.8-rc and the following event log entries are from I think Apache 2.2.15 at
the time.

In all cases a Stop/Shutdown does not kill the lone wolf.

This cause mod_fcgid to become useless cause if mod_fcgid happens to crash,
Apache shutsdowns, the lone wolf continues to answer requests till such time as
it possibly gets old and dies a good death or fcgid crashes again later down
the road and kills the lone wolf. Now your server is not answering requests,
and it usually happens 10 minutes after going to bed (Murphy's Law) and you do
not notice it till noon the next day.

IIRC this was in the Issue Tracker at Sourceforge and included patches to deal
with this on Windows. Why it did not get picked up I do not know. The old
tracker seems to have jumped off a cliff into extinction. However, there are
still breadcrumbs to be found. The attached patch against trunk is based on one
of these breadcrumbs.

Greetings and all credit to Tom.

I believe the caller to procmgr_child_init expects a return or odd things
happen later down the road but will not swear to it. I can't see it hurting
cause after the patch the function literally does nothing but return
APR_SUCCESS. Good explanation of why the bug exists and original patches are in
the thread.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message