Forum Moderators: open
I made an earlier post concerning overload of MySql running on a Win2003 webserver, and by looking through the log files I found out what was happening.
It seems to be a series of IP adresses from Fremont CA, 66.220.20.* that was running through all the pages on one of my sites with ca. 30.000 photos of biological organisms (plants, butterflies etc.), at a rate of up to 10 requests/second, which combined with limited bandwith (756 kb/sec) was enough to make MySql lock up for all practical purposes.
I had to write a script to redirect the IP-adresses to a page where they do no harm; if anybody knows of a more general solution to the problem (perhaps a forced timelap for requests to the database), please let me know.
Does anybody recognize the IP-adresses, or have a clue to what has been happening? I guess it could have been some guys playing with development of a search robot, or maybe even a hack attempt. Is it legal to overload a site with automated requests like that? It certainly took me some time to find out why my server was performing so poorly.
Sincerely Niels from Denmark
That would depend on the location of the server and the place where the requests were coming from. Even if it is illegal, it's tough to get the police (or whatever the proper authority is) to prosecute this type of case unless massive worldwide damage is done.
One other possible explanation may perhaps be that the IP-adresses are a range of proxy servers supporting one user who is trying to download the entire website, so he can browse it locally. Some years ago there was a program called Webdog that could do that automatically.
Anyway, I am really happy that I found the reason and solved it, I had 10 sites down for a couple of days, and that is not very nice.
Niels from Denmark
Thanks
/Niels from Denmark
i wouldnt have though 10 hits per second would be enough to lock up mysql, many forums use mysql as a backend and no doubt they recieve a LOT more than 10 reqs per second.
one thing i know can cause problems is if you were storing pictures/sounds/videos as BLOBs in the database. Also check to make sure that are not performing full table scans unecessarily.
Thanks
Niels from Denmark