System Information

Finally! Since being without power at my datacenter (actually, my computer room (actually, my spare bedroom)) since Sunday, September 14, the power finally came back on last night around 1:00am. Trying to get things back to normal around here…

The webserver is back (obviously), the Personal Video Recorder (PVR) is back, and my Network Accessible Storage (NAS) stack … needs some attention. It booted but all the drives (over 1 terrabyte) are not back online yet. That may be part of the NAS’s internal boot-up verification process, or it might be a problem. Will diagnose — and fix — this evening when I am back in Cincinnati (I am currently in Lexington Kentucky).

UPDATE: The NAS stack is back up and running. Doing final configuration checks to ensure that it’s re-integrated into the server network, but it’s looking promising.

Wow! That was… unexpected!

After a LONG time of not upgrading my site’s operating system, various initiatives I am undertaking required me to update from Fedora Core 5 (released March 20, 2006) to Fedora Core 9 (released May 13, 2008).

I was very nervous about this upgrade since it spanned so many versions of the operating system, but I started out with high hopes. I backed up my system to DVD using MondoArchive, an excellent bare-metal backup solution. Then, I inserted the Fedora Core 9 DVD, rebooted, and started the upgrade proceedure only to be told that one of my drives was a bit short of space (249 megs, to be exact).

The solution ended up being repartioning-in-place using a great product from Acronis which handled all the heavy lifting of the non-destructive repartition for me. I repartitioned the particular drive to a size large enough to make sure this particular problem will never surface again.

Launching the Fedora Core 9 DVD’s upgrade procedure a second time worked, using the newly-widened partition… The installer updated 890 files and rebooted successfully (I was worried about it rebooting successfully!)

However, that’s when I ran into two things… First, the webserver failed to launch because of a configuration error. Secondly, I ran into a time limit and we had to leave for dinner with friends. So, the site was down for a few hours while we enjoyed a very nice meal and evening with Brian, Milan, and Erin.

We came home, went to bed, and I was lying awake thinking of how to address the issues on the server. Next thing I knew, my feet carried me in to the server room and I started tinkering. An hour later (and about 10 minutes ago), I got the site online at last. But there is still more tweaking and testing to do… I need to ensure that the changes I made manually that got the site online will “stick” after the server is rebooted, which I will attempt to do after posting this article.

It was immediately apparent that the new operating system is considerably faster than the old one. Cold-booting takes less than 40 seconds on Fedora Core 9. I’m not sure how long it took on Fedora Core 5, but I know it was longer.

I apologize for the downtime, but it was necessary, and moving forward should be considerably smoother from now on. There is still a fair amount to do — applying non-critical patches & upgrades to the system and then another comprehensive backup, but being back online is enough for tonight.

UPDATE: Rebooting works… mostly. After rebooting, I need to enter “dhclient eth0″, “tzoupdate” and “service httpd start” to get things rolling properly. I need to determine how to automate those steps so the system reboots to an online state.

UPDATE 2: I’ve got the system configured properly now, so it boots into an online state.

Some time during the day on Wednesday, January 9, 2008, the webserver’s power supply stopped functioning and the site was unavailable.

Fortunately, I had a spare power supply at the house and was able to quickly repair the system and get us back online.

I apologize for the unexpected downtime!

Happy New Year, everyone! 2008 started quietly for Wendy & me. We attended a party at our friend Tracy’s house to ring in the new year with our closest friends. Then, for the next couple days, we laid low hanging around the house and enjoying two solid days of downtime. To give some small idea just how low we laid, we watched 5 movies… In one day!

During our downtime, I took the opportunity to upgrade this WordPress installation from version 2.2.3 to version 2.3.2. The upgrade went fairly smoothly, but there were some problems in our existing theme (Ngatini) which required me to use a different theme (Tarski). I am not sure if this is a temporary theme or if we’ll be sticking to it… Tarksi is a modern, good-looking, and well-supported WordPress theme.

I am in the process of tweaking the theme a bit to maximize its usefulness and integration into our site, so some things may not be working as expected yet. They should be fixed in the next several days.

Just a few days after I upgraded to the previous version of WordPress, the new version (2.2.0) comes out. I upgraded today, and it seems to be working well so far.

After thinking about it for far too long, this morning I spent some time upgrading my WordPress installation to 2.1.3, the most current version. I had to update a bunch of plugins to their most current version and then deactivate them one-by-one, install the new WordPress files, then re-activate (one-by-one — WordPress REALLY needs a batch plugin scheme!) them and tweak out the system. Everything seems to be working, but if you spot any weirdness, please let me know.