We have notified you, and I have CCs of the mails, you have a 81MB Access database! This is causing the whole server to stop working while parsing your scripts.
Since renaming the file on your site and sending you the notice, the win13 server has done so much better, you can even see it in the cpu load graphs on SNMP. The site will not be allowed to continue running on JH servers if you don’t move to SQL.
Here is a copy of the mail sent to you May 2nd, 2006 at 5:13am CDT:
Hello USER NAME,
Hope you are doing good. This is regarding domain edited. I found that one of your page is taking 23% cpu, I have renamed that page to 1Default.asp. URL is given below:
http://www.EDITED/forum/default.asp
I found that its using 81.2227 megabytes MS Access DB which could be the main reason, as using MSAccess DB having size more than 4MB is not good for site and server. So, I would like to suggest you convert it to MSSQL/MySQL.
Thanks,
Prakash
Windows Team
This was a notice sent to you on 4/25/2006 at 5:39am CDT:
Hello,
This is regarding the domain edited. Its any of these three pages are creating 23-25% CPU Usage, which is crashing that pool. I have renamed these pages. Please check that page for its coding and its connectivity with databases.
\edited\forum 1default.asp, 1forum_posts.asp, 1forum_topics.asp
I found that you are using MS Access as DB which is 53.2 MB, MS Access can use only 4 MB as DB. More than 4MB can make site sluggish. I would like to suggest you to transfer your DB to either MSSQL or MySQL.
Thanks,
Prakash
So as you can see, the forum grew almost 30MB in a short few days, and we supplied friendly notice each time, we will be forced to turn the site off in a manner you can not restart it if this abuse continues.