Posted on Monday, October 18, 2004 :|: Nobody cared enough to
Comment
The W's Freedom Lube image got a little more attention than expected. I had adjusted settings on my server to prevent it from getting overloaded. Apparently these settings were too tight cause the increased traffic caused the server to throw an error. The error occurred two days after I posted the image. This makes the fourth time this year that this error has popped up. I fixed it pretty quick. I shouldn't have any more problems with the error.
[Warning geek talk]
For those who care to know: I originally set this server up at home so I could work on my college assignments. I used it as an ftp server so I could work on my files anywhere. After a while I decided to start hosting my website here. Since I didn't want the site to dominate my Internet connection, I set the server to only allow 10 consecutive connections. That basically allowed between three and five people to view the site at a time. At that time most of my hits were from search engines, but the site eventually got some real visitors. The first time the server started rejecting request I raised it to 100 consecutive connections. I also fixed a few bugs in the journal code that were causing it to use extra connections. Now I raised it to allow 500 consecutive connections. My low self-esteem makes me think I will never reach this number unless it is due to a DoS attack. If I do reach the max connections I'll have to move my site to a hosting company. I don't think that will happen any time soon.
[/end geek talk]
Update:
I decided to double check before posting this and I found I was wrong. The error has popped up four more times in the last two months. These errors seem to be caused by abusive search engines or some other bots. My logs show over one hundred page requests in twenty minutes on the Rainbo Wonders page. Another log showed a search engine crawling twenty pages in ten seconds. There was a five minute break followed by another twenty pages in ten seconds. My server is not configured for this shit. It is configured as a low traffic server. Uggghhh!! I think all but two of the errors only affected the search engines, but traffic is clearly increasing. I am afraid of raising the max connections any more because these abusive search engines could crash my server. That is the purpose of the max connections. Oh well, I've been planning on moving my site to a hosting company anyways. I just gotta decide which one.
Nobody cared enough to comment.