Got Wills

No worries, it’s back up now. Weird, though. I don’t remember shutting down the computer last night, yet it was off when I got out of the shower. After reviewing the event log after work, I found that it was shutdown gracefully around the time I went to bed.

That’s not the weirdest part, not by far. After getting the computer back up, I was looking through the feeds I subscribe to on NetVibes and saw that my blog wasn’t sending a feed. After trying (unsuccessfully) to ping the virtual server, I go to the trusty start menu and find my Virtual Server Administration links. However, when I open it, “Page not found.” Hmm, IIS isn’t running, after a quick stop at the services console, the WWW Publishing service is running and I’m able to access the Virtual Server console, at which point I’m greeted with a nasty error message… the virtual server service wasn’t running either, that’s odd. Once again I punch the ever faithful “services.msc” in the run dialog and start the Virtual Server service. Only it doesn’t start. Well, well, well, file not found. “Huh? What file?” After a little investigation, I found that the file that is the service isn’t where it should be. “Where is it?” you say… Only my master file table knows.

Naturally, I did what anybody would do in my situation, I reinstalled Virtual Server (I guess not anybody, but I like to think I’m normal sometimes). Anyway, the service was able to start afterwards, but the virtual machine wouldn’t turn on… something about a bad login. Hmm, that’s an odd error for something like this. After beating around the proverbial bush some I figured I’d remove the server and add it again. The processor monitor started moving… it was beautiful.

Naturally, I start a continuous ping to the server so that I will know when the network is available on it, only it never becomes available. Alright, can nothing work today? Well, it turns out Suse saw the network adapter that Virtual Server setup as a whole new adapter. I guess, even though it was the same Mac, Linux knew that something had changed, oh well. A little configuration in Yast and it was responding to my continuous ping. Wondrously, my blog was still returning a page not found, DOH! Back in Yast, I look through the runlevel services and find that lsws is disabled (LiteSpeed Web Server, duh). I start it (and check MySQL, of course). Voila! It’s alive!

The weirdest part… you thought that was it? No, not quite. Actually, I find it freakishly weird that when I found out my Web site was down all night, I got this sick feeling in my stomach. When I had trouble getting back up, I think I actually started to panic. Whew. Good thing I was able to contain my emotions well enough to think this problem through. You would have missed out on this and many more posts only available on Got Wills. Heh, probably not. I would probably just put it back on my Windows PC, you know, the physical (as opposed to virtual) one. I do still feel a strange longing for the 1 or 2 hits that I may have gotten over what I like to call “The Night the Server Went Down in Holbrook.”