Well, I have no idea how I broke my blog, but I broke more than that. I broke my database (though not severly). I ran out of /tmp space. All fixed (obviously) and for those that are truly interested I posted my fix on the WordPress forums. For posterity’s sake, I will post it here as well.
ok, I found it. I got my solution from this post:
http://forums.xmbforum.com/viewthread.php?tid=743964
Yeah, I know it’s not about WP, but it turns out it’s a mysql/system issue, WP just happened to be the code that was trying to query the DB. Tthis was not a WP issue.
I was getting -1 error. I dumped my db to a file. I checked my tables, no errors. I repaired them just in case, no mention of anything fixed. I optimized cause I read it was a space issue. No avail. So I starting cutting off parts of the query, and even the basic select wasn’t working. But this time I was getting an error 28. “perror 28” will tell you “Error code 28: No space left on device”. (Btw, I couldn’t get perror to look up “-1”. It kept trying to use it as a flag.)
Finally a “df” helped me out. Turns out I was out of /tmp space. I cleaned out the extraneous files in there and voila, mysql started working like a champ. Didn’t even have to restart it.
I thought maybe others might be getting this issue, so I thought I would post my fix in hopes of helping other users like me who try to be DIYers.