On Wed, Jan 14, 2004 at 03:27:23PM -0600, Ben Collins-Sussman wrote:
> On Tue, 2004-01-13 at 17:26, Joe Orton wrote:
>
> > Is there still a TCP connection between the client and server at this
> > point? If so, you can identify the server child in question via the
> > server-status output or "netstat -pt", and strace the process to see
> > what it's doing.
>
> After the hang, 'netstat -pt' on both client and server systems shows
> an ESTABLISHED connection:
>
> (client):
> tcp 0 0 10.3.0.6:34027 10.1.8.137:https ESTABLISHED 17769/svn
>
> (server):
> tcp 10055 0 dev37.spdev.colla:https 10.3.0.6:34027 ESTABLISHED 3772/
>
>
> The client is hanging on a select() call:
What's the server doing?
> > The neon debug log output might also help.
>
> Okay, I set neon-debug-mask=130, and attached the last output leading up
> to the hang. See below.
OK, it just looks like the server has hung whilst processing the PUT
request.
If you apply the attached, graceful won't have the timeout errors which
might ease testing.
joe
Index: server/mpm/prefork/prefork.c
===================================================================
RCS file: /home/cvs/httpd-2.0/server/mpm/prefork/prefork.c,v
retrieving revision 1.272.2.3
retrieving revision 1.272.2.4
diff -u -r1.272.2.3 -r1.272.2.4
--- server/mpm/prefork/prefork.c 5 Sep 2003 19:00:53 -0000 1.272.2.3
+++ server/mpm/prefork/prefork.c 27 Dec 2003 06:15:48 -0000 1.272.2.4
@@ -1167,7 +1167,7 @@
"Graceful restart requested, doing restart");
/* kill off the idle ones */
- ap_mpm_pod_killpg(pod, ap_daemons_limit);
+ ap_mpm_pod_killpg(pod, ap_max_daemons_limit);
/* This is mostly for debugging... so that we know what is still
* gracefully dealing with existing request. This will break
