Last Updated: Nov 14,2012
its been erroring out all day
We're really sorry about that and appreciate your patience.
Admin was alerted to the problem at around 6 AM EST, it's been a chase all day, but it is being worked on.
If you have any long or critical posts, please remember to select-all and copy before submitting.
Again - sorry for the inconvenience and frustration.
I just haven't herd anyone ask about it today and was just really curious. My comp is acting up today and I wasn't sure if it was just me or everyone... but then again my phone and tablet wouldn't connect ether so it led me to believe it was everyone.
Yeah, I was surprised by the lack of complaints - but then again, the same issue could be throwing the complaints into the bit bucket and so we're not seeing them.
Glad you posted this!!
Hopefully it will be back to right shortly
As you can imagine, I can't interrupt to ask progress, but as soon as I get word, will let you all know.
it actually errored out when i hit post... wasnt really sure at first if the tread got posted... it was reallt bad this morning but it seems to be getting better now.
Yeah, I was actually one of the first hit by this morning's transient (Murphy's luck lol) and that one lasted 65 minutes.
Confidentially, some staff members have recommended that we replace our server hamsters with caffeine-crazed squirrels for higher energy and I think there's a lot of merit to that idea myself!!
just make sure you have a hot female squirrel and an unreachable nut for the squirrel to chase after! hahaha
Haha! Nice one
It actually started with me this morning around 6am and couldn't jump back on till nearly 10am and it's been spotty since then until now. I've been on here 15 minutes straight with no interruption
Lost 3 posts due to this ah well
Ah - by request from my inbox - Is this the result of a security breech?
Nope, that's not an issue.
From admin - nginx is a web server app that can also function as a proxy server.
And while I've not seen it yet today, you may also see a MySQL 2006 error.
The 2006 error says that there was a network issue that kept our front-end user interface (GUI) from connecting on time with the back-end database (where the posts are really stored). And we've monitored a few of those lately - just saying.
So, this is all some sort of IT problem.
Hope this helps!
Please accept my thanks on your posts as thanks for reporting your issue and sorry that this bit you.
A couple extra thanks is acceptable thanks for keeping us updated with the Info. :thumbup:
I was wondering what was going on, never seen that error before. I had trouble off and on all day yesterday.
It also happened this morning about 6:00 am, seems fine now.
Thanks for the info ...i'm glad it wasn't on my end!
It has happened in the past as well:
I blame all the new S3 users who have dumped their iPhones.
Yep, but this latest round is being persnickity with us.
Admin advised of that earlier transient this morning.
Probably a dumb question, but how would one go about reporting something like this? , email or is there another way?
Not a dumb question at all! Probably the best thing to do is check out this forum: Suggestion Box & Feedback - Android Forums and see if it has been reported or not. If not, create a thread describing the issue you see. That forum gets monitored pretty actively by the Big Guys, so they will see it and respond very quickly.
I purposefully left the discussion here, admin is already aware.
Normally, the suggestion box is the right place.
It's hard to post about the site being down when the site is down.
If you would like to alert admin of special needs, you can email email@example.com or drop me a line via PM and I'll see to it that the right folks are brought in for you.
Thanks for responding guys ... right after that last post i made, i went to all things root subforum and it happened again!
I was trying to get back to this page but kept getting that error message, i tried but could not get back to the site on any page.
Are you aware that there was still a problem about an hour ago?
Yes, absolutely. We're monitoring it as closely as possible and kicking it in the side when that happens until it's properly fixed.
Perhaps, just maybe, you are kicking it in the wrong spot. Aim straight on and a tad lower.
I've notice it yesterday but just a few minutes ago, I received that error screen again.
At least it's no where near as bad as yesterday. Just here and there today
Separate names with a comma.