ML issues?
-
I've had a all working day today. No issues.
-
I've not seen anything over the last 24 hours. Nor have I see any recent issue reports. I wonder if the site gets hit hard from anonymous users for a bit or if there is a background job that runs or something. Locking up that one thread seems to have helped.
-
@scottalanmiller said:
I've not seen anything over the last 24 hours. Nor have I see any recent issue reports. I wonder if the site gets hit hard from anonymous users for a bit or if there is a background job that runs or something. Locking up that one thread seems to have helped.
It is really that thread I think, nothing else. It was a high traffic thread and thus would be visited often at various times of the day.
-
You should be able to still visit it, just not post to it. My guess is that it had something to do with the processes needed to do the updates to it that caused the issues. No idea what it could be, though.
-
I'm looking at the SAR reports now and the CPU has been good all day. One spike four minutes ago to 7% usage but that was all.
-
It has been pretty clear here. Saw one gateway timeout this morning, though, but it was momentary. It was working again as soon as I refreshed the page and very quick again to reload, no delays.
-
Been clear for me the last two days.
-
@scottalanmiller said:
You should be able to still visit it, just not post to it. My guess is that it had something to do with the processes needed to do the updates to it that caused the issues. No idea what it could be, though.
Actually, many times when i just visit the thread it causes gateway issues in my session. Not always, but many times.
-
Just in the Anything Goes thread?
-
@scottalanmiller said:
Just in the Anything Goes thread?
It was multiple threads before, but now that I quit visiting the anything goes thread though no other threads do it. So I am operating on the assumption that it was visiting that thread that caused all issues I was having like that. As that thread was causing site wide issues.
-
I'm really hopeful that we just hit a bug in that thread. It seemed pretty consistent that it was causing an issue.
