Well, as you have probably noticed, my blog was practically down from Saturday evening 21:30 pm until this Monday evening and then blocked, obviously for the following reason:
We have found that your server is using too much processor power. This can have the following causes:
a) A faulty script (PHP, CGI, etc.)
b) An inefficiently programmed script
c) Plugins and cron jobs from web applications (CMS, Gallery, etc.)To prevent further damage, we were forced to block your server immediately.
It's a shame, but somehow understandable, after all, this is shared hosting and if my web server uses all the power, nothing remains on the server for the other customers and thus nobody really enjoys the situation. It is still a shame that my entire account was blocked, including the control panel, and that it was not possible for me to start a log file analysis, because:
Please send us a brief statement and a time during office hours when you can address the problem. We will then unblock the server as soon as possible so that you have access again.
If you have any further questions, please do not hesitate to contact us. You can reach us either via our hotline 0900 xxx xxx (CHF 1.49 / min) or by email at support@xyz.ch.
PENG! And my blog was gone
On that Saturday I carried out the upgrade WP 2.8.5 and was just about to exchange the language files when the whole server 17 flew to my ears. Somehow the database was in an endless loop, staggering between reboot and being available for a few seconds and obviously filling memory. At the time, I couldn't imagine that exchanging language files could be the reason for excessive server load.
So it must be something else, because usually a high load in the case of WordPress means that either the DB is stressed too much or a plugin does not work as it should (improperly programmed or similar), at least something like that can be found when you Sends guys from Google (Reduce WordPress CPU Usage # 1 or Reducing CPU and speeding load time). Since I only put a new plugin into operation on Friday, it can either be this or the upgrade.
Restarting my web server on Monday morning results in the same dilemma as it did on Saturday evening, somehow the DB did not calm down. So I got the idea to first copy the entire WordPress plugin directory onto the site, because the worm suspected it was there. Great, a restart does not result in a loop again, but WordPress was dead. So, get to work and slowly restore the plugins, which worked fine except for the caching plugins. Thus once caching is deleted, reloaded on the server, activated and Eureka! IT LIVES!
So at first I thought that the caching plugins were responsible for the problems. But on closer inspection, my admin backend was suddenly completely in English and this seemed a bit strange. You surely remember the mentioned update of the language files from Saturday? Exactly, I still have it on record and up with …… .- PENG! Goodbye DB!
In wise foresight I already had a new, additional WP installation running in parallel and tried my luck there with an upgrade of the language data ... PÄNG! The DB was gone! So we had the culprit! And as can actually be determined, I was able to WordPress Germany read the following:
There are mistakes that are really embarrassing, like this one, for example. It's the kind of mistake people like to refer to as "how can you be so stupid".
What happened? WordPress 2.8.5 came as a surprise on Wednesday and I was responsible for importing the German version on de.wordpress.org, which is also used as the source for the automatic update. The automation of this system is quite simple: Upload the language file to the SVN, 2 clicks and the release is ready. If it weren't for the human part in this process.
Well bingo! After the last unsuccessful update (I don't mention the version now, just say auto-update) you don't use the automatism and then something like that. Bad luck, it can happen to anyone, it would have been nice if it had cost me a little less effort, hadn't brought the server to its knees and caused my blog to be down for soooooooooo long. Because I missed the crypt a little and as I was able to find out from your emails, you too. Thanks for asking!
By the way, the Frankenstein motif is included as a shirt RetroRebels for £ 23.50.
Hey Ho! Let's go! Welcome back