What the fuck happened?
I submit a thread for judging and then round two is paired up and then......
Website is down for three plus days.
Any idea as to what happened and how we are going to bounce back?
Printable View
What the fuck happened?
I submit a thread for judging and then round two is paired up and then......
Website is down for three plus days.
Any idea as to what happened and how we are going to bounce back?
There was a "coding error" according to what I've heard.
These things don't generally spring spontaneously from the general and standard use of the forum, in my experience, but who knows. The outage was somewhat excessive, but any protracted complaint seems ungrateful for what is essentially a free service given by some.
Until such time as this becomes a repeated issue or it has a genuine impact on activity levels, I'm prepared to forget it happened.
There does need to be a decision about how to proceed with the tournament forthwith though. I would encourage the leadership to view and consider my suggestion posted in the Blender and act with dispatch.
I'm sorry to all the mods if my first post seemed outrageous. It was just sarcasm that it always seems I can never get a speedy judgment, and was not meant to be taken as hostile.
That being said, shit does happen, the real issue is getting the ball back on track.
Even with the downtime, you're likely to get a judgment faster now that there are new judges than many have in the preceding months. Only 3 days is a drop in the bucket of the delay in a time of backlogs.
I will look into it for you, Insanity; I've no outstanding Judgements to deal with, so if it's shown up, I'll get right on it.
I know WitW, but there's nothing else to do, sadly Task stole it from me...
Now I have no excuse not to tidy my room and write my essay on comparative crime theory :(
Heh, the MODERATOR tag looks funny on him....
We had a database cache issue that created a runaway process that hung the server. For some reason, our cronjob to clear the cache stalled and never restarted, leaving the cache to grow too large to be manageable.
Everything seems to have been resolved now. I'm putting a few things in place to help prevent it from happening again in the future. Sorry for the delays and for the confusion. We were a bit puzzled on our end for a while as well.
This technobabble has left me completely satisfied that something beyond my comprehension has occurred and that supermen (i.e. Serillient) have taken care of it for me.
Hooray!
Serillient isn't actually a coder; he's a voodoo priest. He needs to sacrifice a goat and craft a new voodoo doll every time he fixes the forum. It took so long this time because he couldn't find his tribal mask.
Then again, in modern day times he could easily substitute his tribal mask for one off ebay. The ninja ones look close enough.
Sacrificing a keyboard should also do the job.
You know what's hard to find these days? Virgins....damned market for them exploded and the demand is so high that supply can't keep up.
Shame really.
Ah, so that's what happened. Thanks, Serilliant.
Another hiccup today. Similar problem or unrelated coincidence?
The hiccup was server based.
Nothing we could do except bitch to our host.