With the Captain's Log post I got a weird error twice (once trying to view the page the other trying to update it):



When I looked at the database structure I saw it's a mediumint so I updated it to be a bigint. I find it hard to believe this one topic has had this many views...



I think this is one of the only pages accessible to the greater internet without logging into the forums on an account, so I guess it's possible it's just been crawled a fuckton of times.

Either way my change made it so the max value went from 16777215 to 2^64-1 (I guess I COULD have made it be just a regular int which maxes out at 4294967295 but I don't want to have to deal with it again.

Hopefully this means anyone else who happens to be looking at the topic won't see an error (which went away after refresh, presumably phpBB has some way of just saying "yup, I threw an error but they really want to see the topic"

Ok so poking around more I also found we are almost out of disk space so I went looking at at that. Deleted some old old log files but also for some reason the forums had a 5Gb "forum sessions" database file.



I'll be working on scrubbing a bunch of these out, I originally tried to wipe everything where last visit was before Jan 1 of this year but it crushed the system, so I'll do a year or two at a time.

Aaanddd I crashed the sessions table which crashed the database... But it's fixed, and we're back

TL;DR - I deleted everything that was session user id of 1, which I'm assuming is the session value to everything that hits the front page even if they don't log in.



Now we are using half our allotted disk space instead of 96% and things should run a little snappier without the db bogged down like that.