Forum was down for several hours while Martin and I got everything sorted. In short, we had to restore a DB from about 5AM EST, I put the site in matineance mode around 6AM(ish) so it was a slow period, not many (if any) posts were lost.
Chat log from IRC because I am tired:
11:40 <@Manndude> Well here is the series of events
11:40 <@Manndude> Saturday night, MannDude had some beers
11:40 <@Manndude> NOT A LOT
11:40 <+TheHackBoxPie> oh crap
11:40 <+TheHackBoxPie> he franned it
11:41 <@Manndude> The post stats in the backend were broke. They were displaying the wrong numbers for the days. It was saying that prior to the 18th the forum was getting liek 40 posts a day. The 18th we had 777 posts exactly, I remember because it was 777
11:41 <@Manndude> Soooo
11:41 <@Manndude> I do a DB dump, and THEN run the optimize tables tool
11:41 <@Manndude> Things were faster, but I noticed some threads were archived that should not have been
11:42 <@Manndude> So I tried to fix that
11:42 <@Manndude> By turning off archiving and setting it to UNarchive anything
less than 365 days old (everything)
11:42 <@Manndude> then I noticed the CVPS thread went from 700+ posts to 350 something
11:42 <@Manndude> So locked her down
11:42 <@Manndude> Said 'nuh uh, not today'
11:42 <@Manndude> And started drinkign coffee
11:43 <@Manndude> But the DB dump was too big for PMA which is my only point of access to the remote server and doing it via SSH took a long time
11:43 <@Manndude> plus there was an hour or two trying to figure out how to proceed without doing a DB restore
11:44 <@Manndude> That's the RFO
As of now, 11:50 GMT-5, the board is currently unarchiving threads and will be doing so for some time.
That is the screenshot of the post stats now. That is completely wrong and much lower than what it should be. The 18th we had exactly 777 posts.
I believe this has to do with all the thread archiving. I enabled archiving but didn't specify the proper settings, thus damn near everything archived. I goofed, it was my fault. I'm paying the price for it now at noon with no sleep. Everything should be unarchiving now.
The way this works is there is a scheduler that runs on it's own unknown (to me) interval that does this in bulk, 250 at a time. It looks like it took quite some time for everything to archive, so I suspect it'll take quite some time for everything to UNarchive.
That's the RFO for now.
Chat log from IRC because I am tired:
11:40 <@Manndude> Well here is the series of events
11:40 <@Manndude> Saturday night, MannDude had some beers
11:40 <@Manndude> NOT A LOT
11:40 <+TheHackBoxPie> oh crap
11:40 <+TheHackBoxPie> he franned it
11:41 <@Manndude> The post stats in the backend were broke. They were displaying the wrong numbers for the days. It was saying that prior to the 18th the forum was getting liek 40 posts a day. The 18th we had 777 posts exactly, I remember because it was 777
11:41 <@Manndude> Soooo
11:41 <@Manndude> I do a DB dump, and THEN run the optimize tables tool
11:41 <@Manndude> Things were faster, but I noticed some threads were archived that should not have been
11:42 <@Manndude> So I tried to fix that
11:42 <@Manndude> By turning off archiving and setting it to UNarchive anything
less than 365 days old (everything)
11:42 <@Manndude> then I noticed the CVPS thread went from 700+ posts to 350 something
11:42 <@Manndude> So locked her down
11:42 <@Manndude> Said 'nuh uh, not today'
11:42 <@Manndude> And started drinkign coffee
11:43 <@Manndude> But the DB dump was too big for PMA which is my only point of access to the remote server and doing it via SSH took a long time
11:43 <@Manndude> plus there was an hour or two trying to figure out how to proceed without doing a DB restore
11:44 <@Manndude> That's the RFO
As of now, 11:50 GMT-5, the board is currently unarchiving threads and will be doing so for some time.
That is the screenshot of the post stats now. That is completely wrong and much lower than what it should be. The 18th we had exactly 777 posts.
I believe this has to do with all the thread archiving. I enabled archiving but didn't specify the proper settings, thus damn near everything archived. I goofed, it was my fault. I'm paying the price for it now at noon with no sleep. Everything should be unarchiving now.
The way this works is there is a scheduler that runs on it's own unknown (to me) interval that does this in bulk, 250 at a time. It looks like it took quite some time for everything to archive, so I suspect it'll take quite some time for everything to UNarchive.
That's the RFO for now.