Emergency code

By | 28/08/2009

Who to call in case of website emergency?

Due to some yet unknown issue, WordPress version 2.8.2 might be causing server errors.

Lunarpages, my “current” and might become “ex” webhosting company, shut down Gibni.com yesterday without any prior notice, saying they’ve taken an emergency action, as the “index.php” script in my wordpress root was using huge server resources, and could cause a server crash.

First problem is, not only they changed the “index.php” permissions to “000”  (no read permissions) but they took ownership of the file, so neither I could make any changes to the file, nor analyze it for troubleshooting.


Secondly, they made the domain return an “internal server error” to all visitors.


Third, they did not manage to put an “under maintenance” page at the root untill the issue is solved.


Anyway, thanks to my linux skills, I managed to put an “under maintenance” page for Gibni, and get the site back online very soon.


Until I figure out what caused wordpress to eat server resources, and was it really wordpress or Lunarpages’s poor servers and administration, was it the running theme which ran without any issue for months or even the plugins installed on wordpress a year ago; I’ve decided to switch back to wordpress default theme and upgrade to wordpress 2.8.4.

After all, I believe that you should now:


  • Enjoy Gibni, Ad free!
  • Always have a maintenance page and an emergency code, just in case!
  • Be careful choosing your webhosting company!

Leave a Reply

Your email address will not be published. Required fields are marked *

CommentLuv badge