That problem does not ring any bells, but you could try adjusting the MaxRequestsPerChild (APache 1.3, similar or the same in Apache 2.x) setting for Apache to force the child processes to die after processing a certain number of requests --- the default of "0" allows them to stay alive as long as need be (or as they can). processing requests. It's more useful if you have apps running under Apache that leak memory, but it might be useful here in mitigating the problem.
Of course, if you're already doing this, then never mind... :-) Hope this helps... Regards, Joel Parramore -----Original Message----- From: Jessica Ruble-English [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 6:40 PM To: CF-Linux Subject: CF5/Apache goes dead Our servers get maybe 1-2 dozen of those type of requests each day, but nothing serious. :( I may install an apache restart script for now, but I'd feel a lot better about solving the problem rather than just duct taping things together. Any other ideas? Jessica On 6/20/2003 11:16 PM, Paul Rosenberg wrote: > We experienced a similar type of problem a while back. The cause was traced > to an attack from the web trying to infect our server with a Windows virus. > The virus was unsuccessful since we run Linux/Apache/CF5 but the number of > Apache processes kept increasing until the setup stopped working. > > Initially we installed chron job which constantly checked the number of > open processes and restarted Apache whenever the number went above a > setpoint. While we had a temporary halt, there were no major disruptions. > But not too elegant. We then worked on our firewall to reject the offending > sites but new offenders keep popping up. > > I also would be interested in solutions that others may have used. > > Paul > > Every few days something strange happens to our > > webserver. The server will appear to be functioning > > normally (plenty of free memory, free swap space, etc) > > but the web server will stop responding, the load will > > go to flat 0, and apache will have its maximum number of > > child processes running (per the MaxClients setting). > > > > Just restarting apache will fix the problem for > > a few hours, but the prolbem inevitably returns, but > > if I restart apache AND CF, the problem goes away > > for a few days. > > > > Any thoughts? Any particular information I should > > send along? > > > > Jessica ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=14 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=14 Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.14
