Oh well, as you probably have realized, was practically my blog from Saturday night 21:30 today Monday Locked down until evening and then, This obviously made the following reason:
We have found, that your server takes too much processor power. This can u.A. following reasons:
a) A script error hafts (PHP, CGI, etc.)
b) An inefficient programmed scripts
c) Plugins and cron jobs of web applications (CMS, Gallery, etc.)
To prevent further damage, we were forced, Your server to lock immediately.
Damage, but somehow understandable, Finally, it is here to shared hosting and if my web server claims the whole performance, nothing remains for other users on the server and therefore no one has really enjoy the situation. Too bad yet, that equal my entire account has been blocked, including the control panel, and it was not so possible, a log file analysis to tackle, because:
Please let us have a brief statement and get a date during office hours, in which you can take the problem. We will then unlock the server as soon as possible, so you will have access.
If you have further questions, We are of course at your disposal. You can contact us either via our hotline 0900 xxx xxx (CHF 1.49/min) oder per E-Mail an firstname.lastname@example.org.
PENG! And gone was my blog
On that Saturday I had the WP upgrade 2.8.5 carried out and was just about to replace the voice files, as me the whole server 17 flew around the ears. Somehow the database was in an endless loop, vacillated between the reboot and sekündiger accessibility and obviously filled Memory. I could not imagine at that time, that an exchange of voice files can be the reason for excessive load on the server.
Thus it must be on something else, because usually means a high capacity utilization in the case WordPress either the DB is overloaded or plugin does not do as it should (unclean programmed or similar), something you can find at least, when one of the guys Google unleashing (Reduce WordPress CPU Usage #1 or Reducing CPU and speeding load time). As I lived on Friday took a new plugin in operation, It can do this either, or just the upgrade is.
A restart on Monday morning my web server results in the same thing again, As already Saturday night, somehow calmed no longer the DB. Thus came the idea, until the whole of WordPress Plugin Directory to copy the page, because the worm suspected there. Before, A restart does not result in a loop again, dafür war WordPress tot. Also, to work and slowly restore the plugins, was bis auf die Caching Plugins prima klappte. Thus, once caching deleted, reloaded onto the server, activated and Heureka! IT LIVES!
So I thought at first, that the caching plugins, responsible for the problems were. However, a closer examination, was my admin backend suddenly completely in English and this is a little strange unsuspected. You remember the mentioned update the language files from Saturday? Exactly, I was still up with on board and…….- PENG! Farewell DB!
The foresight, I had already developed a new parallel, tried another WP install and run on my luck with upgrades he Sprachdat…Pang! Way was the DB! So we had the culprit! And had actually determine how, I was at WordPress Germany read the following:
There are errors, are but a really embarrassing, like this, for example,. It is the kind of mistake that you like as "how can one be so stupid" means.
What had happened? On Wednesday came WordPress surprising 2.8.5 and I was responsible for bringing in the German version on de.wordpress.org, which is also used as a source for the automatic update. The automation of this system is quite simple: Language file upload to the SVN, 2 Clicks and the release is ready. Were it not for the human part of this process.
Bingo! Since you used to last wayward Update (I do not mean the version erwähn, 'm just AutoUpdate) automatism not already and then something like. Pitch, can happen to anyone even, would have been just fine, it would have cost me a little less effort, the server is not forced to his knees and made for an soooooooooo long failure of my blog. For me, the vault but lacked a little and I was able to experience through your mails, you also. Thanks for asking!