httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Smith" <g...@primeexalia.com>
Subject RE: [users@httpd] Apache 2.0.52 - stops responding
Date Sun, 03 Oct 2004 01:18:42 GMT
Travis, 

What's the count of established connections?  They wouldn't by change be
coming from the same IP holding your connection open would they?  The
time_wait is waiting to receive a response back I think.  It's been a
while since I dug through TCP stuff.  Anyways, you can have a big
backlog queue without problem.  But if there are active connections and
they are processing slowly (or hanging) then until they timeout Apache
will continue to try to server those few.  Increasing the max
connections in this case will have no effect.  



> -----Original Message-----
> From: Travis Derouin [mailto:tderouin@gmail.com]
> Sent: Saturday, October 02, 2004 3:57 PM
> To: users@httpd.apache.org
> Subject: [users@httpd] Apache 2.0.52 - stops responding
> 
> Hi,
> 
> I'm running Apache 2.0.52, with resin 2.1.14 on a Windows 2003 server.
> The past few days we've been running into a weird problem, I'm not
> sure whether or not Apache is responsible. Every few hours (our site
> gets about 70k visitors a day), all the Apache worker threads get used
> up and the server comes to halt. Doing a netstat -an, there are a lot
> of sockets that show up as being either in the CLOSE_WAIT, TIME_WAIT,
> or FIN_WAIT2 state.
> 
> Example:
> 
>   TCP    69.20.122.206:80       165.155.160.139:62360  FIN_WAIT_2
>   TCP    69.20.122.206:80       167.80.246.204:10384   TIME_WAIT
>   TCP    69.20.122.206:80       167.80.246.204:10392   TIME_WAIT
>   TCP    69.20.122.206:80       167.80.246.204:10401   TIME_WAIT
>   TCP    69.20.122.206:80       24.69.255.205:9963     ESTABLISHED
>   TCP    69.20.122.206:80       24.77.151.229:1743     CLOSE_WAIT
>   TCP    69.20.122.206:80       24.78.22.115:4466      CLOSE_WAIT
> 
> When the process halts, of the 700 or so open connections to port 80,
> 500 of them are in one of these 3 states (400 are CLOSE_WAIT).
> 
> It's weird, everything was up and running for almost 3 months without
> any problems, then since 9.29, apache comes to a complete halt every
> few hours, depending on the traffic. We haven't run a windows update
> since 9.15, so I doubt there's been anything new put on the machine
> that's interefering with Apache. The worker threads seem to get used
> up almost immediately before there's a crash, things will seem stable
> according to the server status, with about 200 threads in use, then
> it'll jump by a hundred per minute over the next few minutes until it
> hits its max (at 1400) then everything stops working.
> 
> Could the hosting provider have changed some network configuration
> that might interfere with our Apache process? We also had the same
> issues with 2.0.49, and I upgraded to .52. We haven't made any
> significant code changes in the past month that might be responsible
> for something like this.
> 
> Any input would be appreciated! Thanks!!
> Travis
> 
> ---------------------------------------------------------------------
> 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


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