Page Source:
Date:
© 2003 Red Wolf %57%65%62 %44%65%73%69%67%6E — All rights reserved

Corrupt Database

If you were wondering why the site was down yesterday, it was due to a corrupt database. Berkeley DB spat the dummy over a locked file and threw a spanner in the MovableType works.

After a very late night of reinstalling MT, all posts are back online. Unfortunately a few comments posted over the last six weeks got eaten in the move. And reimporting the posts has meant they now have exciting new locations, which is a bit of a bugger for anyone linking to the site.

With any luck, the back end will soon be moving to a more stable MySQL database and this sort of problem won't be happening again.

© 18.12.2003 redwolf in site

Comments


Hmm... when databases go bad, or when databases attack! Now that'd make a great geek tv show. — posted by lucie at 18.12.2003 17:16 AEST | #

Just imagine... someone out there is, even as we speak, running their blog on MS Access. We've escaped lightly : ) — posted by sbszine at 19.12.2003 09:59 AEST | #

MS Access... Now, I'm scared — posted by Red Wolf at 19.12.2003 10:24 AEST | #

I feel your pain. In fact, I've felt your pain. Twice before. The fun part is wondering what people think as they arrive at the wrong pages from Google. It took over a month for Google to reindex my archives correcting the situation. I did have to manually change a few entries after reimporting them in order to ensure that certain entries were at their old numbers. These were entries that had been linked to via media or uber-bloggers. Fun stuff, that Berkeley. My last meltdown came courtesy of that Lolita spammer jackass. I'm now running on MySQL. — posted by James Landrith at 20.02.2004 02:08 AEST | #

Post a Comment







Remember personal info?






Not all browsers automatically refresh. Please do not assume it's failed and hit Post again. We will just end up with multiple copies of your comment. Duplicates will be removed.