Check the content of your .htaccess files. It sounds like they may be screwy.
this is the content of my htaccess :
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
I received a e-mail from my host saying that my SQL Server load is so high .. what does this mean ?
I received a e-mail from my host saying that my SQL Server load is so high .. what does this mean ?
Generally, it means that your host sucks and oversold your machine, or you’re getting too much traffic for such a cheap hosting service.
You can try installing WP-Super-Cache, but honestly, you’ll probably want to switch to a better hosting company.
Before the server crash I had no problem the blog was very very fast .. I was quite happy.
I running my blog as single website on 100Mbps 1GB Ram dediacted server.
Even when I reach 300 simultaneous visitors my max Ram usage is about 300 Mb.
Now with the blog running slow I have a traffic drop and event with 30 users connected I have 800 Mb of my Ram used.
I think my host is one of the best in europe LeaseWeb .. don’t you think ?
I am really stuck .. I tried to disable all plugins .. reboot my server .. restart apache2 and mysql .. disable services ping .. remove url rewrite .. trying several old backups. Finally it seems when my server crashed with the PHP script something messed up maybe apache or SQL.
If I use an old backup the server become fine and super fast again, but once I publish,delete,edit post it begin overloading again.
if anyone know ho to fix this problem I’ll be very grateful for the rest of my life !
If I use an old backup the server become fine and super fast again, but once I publish,delete,edit post it begin overloading again.
WordPress makes HTTP requests back to itself, in order to run processes asynchronously. A normal webserver setup allows this. If the DNS is broken or a firewall interferes or anything breaks it, then the site will bog down.
So basically, your host is configured improperly, so the wp-cron jobs cannot run. There’s lots of ways that this can happen. The most common cause is broken DNS settings, but anything that breaks a site’s ability to access itself as the site via the webpage will cause it.
Install a plugin called WP-Crontrol. This will let you edit or remove the wp-cron jobs which are bogging down your server.
Thanks for your answer.
I think that means I have a problem on my bind server.
I will try WP-Control and tell you the result.
is there any known settings to avoid my overload problem ?
Can deleting wp-cron.php solve the problem ?
Can deleting wp-cron.php solve the problem ?
No. The hits will still try to happen, they just won’t work. The problem is that it’s trying to hit that over and over, because it’s not actually hitting it and making it run. You need to make the cron jobs run, so that it stops trying to run them.
You can force the wp-cron jobs to run using a real cron process somewhere like this:
Make a copy of wp-cron.php and call it “my-cron.php” or something else. Keep whatever the name is a secret. Then remove these two lines from your new copy of the file:
if ( $_GET[‘check’] != wp_hash(‘187425’) )
exit;
This allows you to hit the file from anywhere (even a browser), and force any scheduled jobs to run. You’d hit it from a normal, real, cron job by calling the URL via curl or wget or some such thing.
Thank you very very much I just copied the content of my wp-cron.php then created a wp-secret_name.php, removed the two lines you gave and hit the file from my web browser : http://www.mysite.com/wp-secret_name.php
it took a long time to wp-secret_name.php to end loading but finally my blog came to its normal status, very fast and with a normal Ram usage
Just one problem remaining : when I try to edit,publish,delete a post the overload comes back
So should I hit wp-secret_name.php via my browser every time I edit my blog ?
Is there a way to make this php file hit automaticly every time I edit something on my blog so that the problem will disappear permanently.
I want just to add : after the end of loading wp_secret_name.php I have this message :
Warning: fsockopen() [function.fsockopen]: php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution in /home/mysite/public_html/wp-includes/class-snoopy.php on line 1158
Warning: fsockopen() [function.fsockopen]: unable to connect to www.google.com:80 (Unknown error) in /home/mysite/public_html/wp-includes/class-snoopy.php on line 1158
Warning: fsockopen() [function.fsockopen]: php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution in /home/mysite/public_html/wp-includes/class-snoopy.php on line 1158
Warning: fsockopen() [function.fsockopen]: unable to connect to submissions.ask.com:80 (Unknown error) in /home/mysite/public_html/wp-includes/class-snoopy.php on line 1158
Warning: fsockopen() [function.fsockopen]: php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution in /home/mysite/public_html/wp-includes/class-snoopy.php on line 1158
Warning: fsockopen() [function.fsockopen]: unable to connect to webmaster.live.com:80 (Unknown error) in /home/mysite/public_html/wp-includes/class-snoopy.php on line 1158
maybe this code can explain my server overload
Just one problem remaining : when I try to edit,publish,delete a post the overload comes back
So should I hit wp-secret_name.php via my browser every time I edit my blog ?
Is there a way to make this php file hit automaticly every time I edit something on my blog so that the problem will disappear permanently.
… I think you’re missing the point here.
Hitting that wp-cron.php file automatically is exactly what it is supposed to do. That is, in fact, the problem. So asking me how to make it hit it automatically is a bit silly, because it does hit it automatically. That is your whole problem, that your server, for some weird reason, is not allowing that to happen.
php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution
Again, this points to a misconfiguration with your DNS setup. The webserver can not figure out who “google.com” or “ask.com” or “live.com” is, in your particular case. You need to fix the server, or have your host fix it. These errors in particular probably are from the Google Sitemaps plugin trying to contact those sites to inform them of a new post. But because your server is not allowing name lookups to work, it can’t talk to anybody outside itself.
This is likely the same reason that wp-cron is not being hit properly. The server cannot find its own name via DNS, so it can’t call back to itself.
Thank you 100000000000000000 times again, you are the only one who could help me. I’ve been browsing too much forums threads to figure out what’s wrong with my blog but no one gave me the answer.
I hope this topic will help people having the same issue with their wordpress. There is one solution to this : change your crappy host.
I recently moved to a new server and everything is fine, my blog’s fast than ever.
Hi,
I’m using WordPress 2.8.1, and my server also encounter the high load issue (load average > 70+).
I’m trying to to edit the wp-cron.php, that you have mentioned in your previous post, but i can’t find the below code that you’ve said.
if ( $_GET[‘check’] != wp_hash(‘187425’) )
exit;
May i know what i can do to solve this problem?
Thanks a lot and sorry for my poor English.
Hi,
To add on, I’ve also checked the table “option” from my db.
I found there’s many “no” in “autoload” column.
e.g:-
option_name:’_transient_timeout_feed_mod_a5420c83891a9c88ad2a4f04584a5efc’
option_value:’1248245864′,
autoload:’no’
can i know what it mean, and is this causing my server high load? How can i solve this problem?
Thanks and appreciate your help.
