Nope, didn't notice it, and I certenly didn't just fix it either.

The underlying problem was this:
145 = Table was marked as crashed and should be repaired

Not sure what in the code is causing the online table to break it's self every week or so at most. Watching it overtime, it's overhead will grow to a huge ammount, and I think eventually just cause problems due to it. Anyone know any easy ways of dealing with a relativily small table in mySQL that gets changed quite a bit, and also deleted from? To me, this shouldn't be normal, and I don't like the idea that I need a repair statement in my crontab for the BBS. But I've never had to do this with RioCar.org, and it has a similar online table...