RSS 
So right after that last loverly post I go and update my server because of some GLSA's sugested I do so and poof, broken. What it was is that Mysql upgraded to 4.1 from 4.0 and they aren't compatible. There is a proper upgrade procedure. So I downgraded and had a small heart attack when mysql still wouldn't come up. After some poking around I disabled Inno DB support and it loads up fine now. Thankfully none of my data is Inno DBs, just ISAM ones. ::Phew::. But totally annoying and worrying for a bit. Anyways, I don't have time to do the upgrade now so I'll probably do it tonight after work. Still, one might ask that portage could have at some point more forcefully warned me that in this routine upgrade suggested because of a exploit would make my data inaccessible (and possibly corrupted) unless I followed the upgrade instructions. I'm sure I'm not the only person who has had this problem ;).
The upgrade guide for Mysql 4.0 to 4.1 is here.
Nothing like mysql failing to make you realize how important it is, as in pretty much all my data on my server is in it and dependant on it. My blog, gallery, and wiki. Access to my email (vpopmail and squirrelmail). And several other miscellaneous utilities.
Update: Ha, and then apache took a kit in the pants to restart. Failed the first few times for unknown reasons (probably new init file stopped it improperly preventing it from starting). Manually started and stopped apache and then it was fine.
