Sorry, I don’t think there is anything I can suggest, other than to contact hostgator. If your blog is causing a lot of strain on their server. I would suggest installing WP Super Cache to relieve some of the pressure.
Harmack…i had done with cache plugin to relieve the strain..but still dont know why its happening..:( I had checked all domains on that server and also removed all unnecedssary files from cpanel.
Somebody can help me what is the reason now..??
What can’t you access?
What is your website URL?
What did hostgator tell you?
Hostgator send us the Ticket:
Hello,
I apologize, but I was forced to suspend the directory
“/home/gauravhm/public_html” as multiple scripts inside it were
causing a a high load on the server, and due to it affecting all of
the other accounts on the system, I forced to take immediate action
for the health of the server.
and….lots of
Right.
So what is your website URL? Do you have any non-wordpress scripts in there? Did they identify what scripts specifically were being accessed?
Hey harmck..is it dangerous to paste here all content in Ticket..or what?
Depends on the information it includes, such as your personal info etc.
have you tried emailing them ? or calling their support ?
[sig moderated as per the Forum Rules]
This isn’t really a WordPress problem, it seems something is up with your website hosting. If you have a high volume traffic website, you should potentially seek a hosting company who can cope with these high volumes of traffic, as hostgator shut off your website, and they don’t seem to be too helpful in getting to the root of the problem.
They are the only people who can help you track down the root cause of this.
yes I got the Ticket mail from them..
I think wp-cron.php file become reason for traffic… but how can i find out that file’s function..?
Turns out this is a common occurrence and many people on hostgator have found this.
On googling the problem I found a few blog articles related to it.
http://blog.mellowhost.com/how-to-stop-wp-cron-php-from-firing.html
In the above article it suggests:
You can also put the following in your wp-config.php file to set DISABLE_WP_CRON global variable to TRUE:
define('DISABLE_WP_CRON', true);
Hope that works out.
