Kdawg wrote:
Was that the cause of the whole site being slowed in loading yesterday?
Yes.
And just for the sake of talking, here's a few stats for you. Since day one, traffic has been increasing. To the point that thursday was probably one of the heaviest yet, at 5.6 gigs of transfer in just a single day. And I suspect friday and today would have continued the trend. And that's fine as far as it goes. But then the spammer/flooder also increased dramatically the total number of hits on the server.
<center>
<img src="http://mtm2.com/~forum/images/webstats20040924.gif" width="520" height="408"></center>
The two things we're interested in that diagram are the green and the red bars. The green shows the number of http hits on the site and the red shows the amount of transfer. When I turned off the bbs, the hits dropped like a shot. When I turned off the files, the transfer dropped. However, you have to note that that's just http (not ftp) and it doesn't measure system resources or monitor the apache server.
Normally, the cpu load is less than a couple percent. And the majority of that is dedicated to running the server and delivering files. Welp, yesterday, when the bbs busted, that put resources up over forty and fifty percent, and attempts to fix it actually made it get worse before it got better. A hidden thing in this mix is the number of connections that the web server allows, and it's not listed anyplace. So, what was happening was the bot/spammer/lamer/flooder sucked up all the connections so that when we tried to access the site, apache, the server, said, uh, all connections used up... you'll have to wait until they're free again, which, of course, they never were. Add to that, broadband d/l managers leaching files. In this case, the network card is working like a pipe. You're trying to force eight inches of water through a one inch pipe. Something isn't going to fit, not everything is going to get through. That accounted for much of the slow down as well.
The trick, then, was trying to pin point what was doing what. I'd find something, fix it, then the change wasn't what it should have been... because there were several things at work. It's these sort of situations that made me reluctant about running our own server. I'm not at all confident I'll always be able to cope and deal with these problems. This time, however, we got lucky - and I hope that's the end of it again for another little while.
Meantime
248 days, 13:50 without a reboot ;-)