I saw the same issue. I don't know if uploading was affected, as I didn't try, but opening forum threads didn't work. Strangely if I logged off the forum would work, but when logged in it wouldn't.
Posted under General
Mr_GT said:
Is there any way we can fix this or at least turn off the problematical scripts like the tag history pagination? Maybe it's those scripts that's causing the problem.
albert said:
I noticed that someone or something was hitting the tag history pagination pretty hard which was causing load on the database server to spike to 12+. I've since changed the pagination method and things seem to be normal again.
It's been over a day since the switch to the (broken) Prev/Next system...
RaisingK said:
It's been over a day since the switch to the (broken) Prev/Next system...
Seem the switch was only a temporary solution then since it came back rather quickly. Now if the tag history program/script isn't the one that's causing these recent failure are there any other program/script one could think of that could affect this much of Danbooru?
Updated by Mr GT
Bloodletter said:
Don't know if it's just a coincidence, but I was having trouble uploading, updating tags, reading forums, etc. until I cleared my cookies (ie: logged in and out) and cache. It's all running smoothly now.
Total coincidence, failboorus are serverside so nothing you do clientside is going to stop them.
Just to repeat what others have already said, I've been getting Failbooru when trying to do tag edits (the edit still ends up going through though) and when trying to read any thread on the forum that has new posts (threads without new posts work fine). Trying to hide certain posts in the mod queue is also giving some ridiculously long error message that prevents the post from being hidden.
It seems to happen around the same time daily, roughly between 3-5 PM (PST), although today and yesterday felt like it got even worse.
Updated by ultima
Hmm, so among the things I am seeing failing are: viewing an updated forum thread where the last read information would need updated (logged out works fine, viewing threads that hadn't been updated seems to work too), hiding certain posts in the mod queue, and adding favorites.
The one thing those functions have in common is that they need to update things on at the user level. Perhaps the users table is somehow causing these issues?
Last night I could open the thread list but not any actual threads, and could vote and favourite posts but not edit tags - altough sometimes a tag edit would go through despite the error. In particular I could neither edit tags nor comment on post #769909.