Today I had a kind of a scare. This morning, I noticed that this blog was down. My first guess was that it should probably be related to the intermittent outages my host was facing.
The blog was sending back 500 – Internal Server Error responses. The
error.log file was filled with messages like these:
[Tue Nov 24 10:38:42 2009] [error] [client 22.214.171.124] Premature end of script headers: index.php [Tue Nov 24 10:39:23 2009] [error] [client 126.96.36.199] Premature end of script headers: index.php [Tue Nov 24 10:41:05 2009] [error] [client 188.8.131.52] Premature end of script headers: index.php [Tue Nov 24 10:41:46 2009] [error] [client 184.108.40.206] Premature end of script headers: index.php
As usual, I looked for help on the WordPress Forums. When the initial suggestions did not resolve the problem, I decided to dig deeper. I downloaded WordPress and extracted a clean install. All I did was moved over this blog’s
wp-config.php into this directory. It again resulted in the same 500 – Internal Server Error response. That almost certainly indicated a corrupt database.
Thankfully, reverting to the last good backup is fairly easy in DreamHost Panel. The Restore DB option is available under Actions for each database in the Main Menu → MySQL Databases section of the panel. After restoring the database, the blog was back up and running.
Now, only thing bothering me is – what caused the database corruption? Was it some server glitch, that would hopefully never happen again? Was it a plugin (like IntenseDebate, etc.) that misbehaved? Or a blog management client (like WordPress for BlackBerry, etc.)? Not sure. But the mystery does make me nervous. But for the time being, things look OK!
Chrome OS Update
In my last post about running Chrome OS in VirtualBox, there are some screenshots. As you can see, the default screen size of
800x600 is pretty tiny to do anything useful.
To increase the screen size, I tried two ways I would have tried for any other Linux guest:
Not sure why, but I could not install any Guest Additions to the Chrome OS running as guest.
I tried to update
/etc/X11/xorg.conf to define screen modes (by first dropping to a shell using
ALT + CTRL + t – which, by the way, does not always work for me ). But Chrome OS would not let me save the
/etc/X11/xorg.conf, even with
sudo. Is this normal?
In any case, I had to take the long route. Updating
~/chromiumos/src/rootfs_static_data/common/etc/X11/xorg.conf and re-building the image. But it worked! Now I am running Chrome OS in
1024x768 mode, which is so much better!
That is it for now…