ANNOUNCEMENT SERVER OUTAGE 12/29: (Update: 4:31am - We're Up)

[signbabybrady]

You must have accidentally hit the brackets. Hit the three dots, and then hit the brackets and it will toggle everything back on for you:

Some day I'll make a FAQ thing here for things like this. You know, it's only been 20+ years. I'm clearly a little slow on stuff like that

Thanks that did the trick

 

[IcyPatriot]

We're up ...

 

[Ian]

Thanks that did the trick

Lol, good deal. Like I said, I’m way behind the eight ball on having answers to that stuff readily available. I definitely need to finally be better about that heading into 2025.

 

[WhatJustHappened]

I thought it was going to stall/time out again just now, but it recovered just before the timeout would normally pop up

It's weird, it always seemed to happen most of the time late at night, when there's very little traffic.
I was hoping that was a part of the upgrade, not sure what that entailed though.
Just an FYI Ian.

Thanks

 

[Zuma]

Is it possible Search needs to be re-indexed? I can't locate one of my posts.

Edit: never mind search found it

 

[Ian]

Test

Is it possible Search needs to be re-indexed? I can't locate one of my posts.

Edit: never mind search found it

I re-ran this again this afternoon. Should be all set. When I ran the update last night, that table tends to have an issue due to its size anytime it's backed up, but I think it's good to go now.

 

[One-If-By-Sea]

Definitely faster. Thanks.

 

[Zuma]

I seem to be running into more "Not open for further replies" then usual. And that's on recent threads within the past 6 months. Is it possible that is the result of the server move?

 

[Ian]

I seem to be running into more "Not open for further replies" then usual. And that's on recent threads within the past 6 months. Is it possible that is the result of the server move?

I think the cron that closed the threads after a certain amount of time might not have been running on the old one, and now it's able to function correctly, so that could be why. I'll have to look to see what the cutoff is, but that's likely the reason. Might have happened when I re-indexed and re-cached everything.