Moar downtime? who was playing with bots again?
-
I can still drag and drop images into this box .... image needs to be stored somewhere.
-
Oh, true...but it's not downloading everything and caching them. That's what I was thinking of.
-
It started before lunch time for me.
-
@apapapapaidmolollsldl.
That joke was funnier as a running gag in that "Godzilla" movie with Matt Broderick.
-
Typically those types of failures are environmental, the download file is > max size, the timeout was exceeded, max query size exceeded, etc.
What it means in terms of discosauce? I don't know. Not going to go look either. I'll just file it away and rock against my knees in my safe place.
-
After you upgraded to 4GB I am getting more white-sites again where Discourse doesn't load anything. Are we using all 4 GB not even a day after you upgraded or is my connection spazzing out and making things look bad just for me?
Filed Under: We clearly need 128 Gigs of Ram for a boad with us as users!
Addendum: Obviously not as bad as right before the upgrade but it's still weird!
-
After you upgraded to 4GB I am getting more white-sites again where Discourse doesn't load anything.
I just got a whitescreen on opening a PM.
Are we using all 4 GB not even a day after you upgraded or is my connection spazzing out and making things look bad just for me?
-
I had never gotten a whitescreen until just now, on the main topic page.
-
The white pages are because the RAM hasn’t been filled up yet with bytes, so there are a lot of page faults.
-
Open a Java app on the server, the memory will be all bitten up.
-
-
The white pages are because the RAM hasn’t been filled up yet with bytes, so there are a lot of page faults.
TDEMSY....wait, this is Discurse. Maybe it does.
-
Memory appears totally fine on the server.
root@what:~# free total used free shared buffers cached Mem: 4049440 3164340 885100 0 71432 1572272 -/+ buffers/cache: 1520636 2528804 Swap: 2097148 6428 2090720
In fact it is so high I think I will add another worker (2.5 gigs is free)
-
White screens are
ActionView::Template::Error (incompatible character encodings: UTF-8 and ASCII-8BIT)
AGAIN.Its killing me... why is it only happening here, what kind of voodoo magic are you doing that is causing rails to burn.
-
Memory appears totally fine on the server.
BTW I got two white-screens in the space of a minute after making the post right above yours.
-
-
Yeah, I can see in the logs.
-
I don't know if it is helpful or not, but during this last blackout period I received multiple email notifications that were the same. They were sent 1 minute apart. I can forward them to you if they would be of any assistance.
-
And that link does not work for me. It is encoded to be redirected and tracked, but is not doing so.
-
My link? It was just to Nancy Pelosi trolling the entire country by asking "Are you serious?"
-
Well, this is what I got. Nothing. Just a URL and not even a 2XX, 3XX, 4xx response. Just...nothing.
-
When did that happen? logs have been clear ever since I brought the instance back up.
-
Weird because I clicked it again and it seemd OK fro me.
Here's teh bare link
http://www.youtube.com/watch?v=08uk99L8oqQ&t=14
-
I just checked it, and it is still happening to me. Anything I can do to gather more information for you?
-
That works for me, the first link gets me fuckall.
-
Maybe your browser was stupefied by using Discurse?
-
A blank screen with 200 OK? That's worse than an error message saying "there was an error".
-
There is a good chance that Ctrl+F5 would fix it, but I wanted to give @sam a chance to gather information before I did so. I am apparently an edge-case because this shit always happens to me.
-
Nothing? Alright then, hard refresh it is.
-
@sam, a hard refresh does nothing. The link is still dead to me. Not that I wanted to see it anyway. Nancy Pelosi is a cunt, but still.
-
@Intercourse said:
Nancy Pelosi is a cunt, but still.
So there's a point where the horror outweighs it after all, eh?
It's all right, I was just trolling Sam. I would assume it's only happening here because it's TDWTF.
-
My link? It was just to Nancy Pelosi trolling the entire country
@Intercourse said:
Not that I wanted to see it anyway. Nancy Pelosi is a cunt, but still.
Thanks for the warning. You saved me from spoiling my dinner.
-
Thanks for the warning. You saved me from spoiling my dinner.
Fortunately it was only audio--that would only cause minor curdling.
-
According to your great leader's q&a site, the error is due to someone's code having been written in an editor using the wrong encoding?
who the fuck is that doofus?
And, is it possible that some small piece of incorrectly encoded code is getting loaded at runtime on a random (or whatever) basis that causes ruby to shit itself?
-
I have a suspicion that you either copy/pasted a part of your Haml template into the file
Really? Someone who goes to SO would make copypasta? The hell you say...
-
@Intercourse said:
Really? Someone who goes to SO would make copypasta? The hell you say.
I just had to deal with some douchebag that edited an XSL file for our website using the wrong encoding, and ended up dumping trash characters into all the inline javascript. The page errored so bad that IE flat out refused to render it and would attempt to reload it, causing an infinite reload that looked like the old infinite redirects problem that used to happen before browsers were able to detect that situation.
-
some douchebag that edited an XSL file for our website using the wrong encoding
Many years ago, I did the same thing. I should have added that to the programming confessions thread.
-
In my defense, we cannot all be born as a god to programming as @blakeyrat was. Some of us had to learn. ;)
-
But you at least tested, saw that it was broken, and fixed it... right?
This asshat did it 2+ years ago. It was only broken in the CMS's GUI editor/preview. Well they apparently never bothered to use those, and just published shit to see if it worked. Our marketing editors complained that the site was broken in the editor/preview and the contractors couldn't figure out what was wrong or how to fix it, so they just told the marketing dept to publish to test and skip the preview part.
2 years later a different contractor was working on the site and calls me because none of the fucking shit works in the CMS. So I went spelunking and found that gem, which took a measly 15 minutes to find and fix (there were a LOT of trash characters, and just a straight conversion didn't fix it).
-
2+ years and they never fixed it? Man, that is pretty horrible.
My SNAFU was fixed before the end of the day. IIRC, mine happened because I was using another computer and a text editor I was not familiar with. It did not last 1/5 of a decade.
-
I have never really opened the network tab in Chrome while using Discourse. Is it normal for so many JSON POST methods to just hang for 15s at a time? Every one of them is 15.08s and 241B.
-
At first they didn't want us (internal programming dept) to deal with our website because they saw us as a hindrance to meeting deadlines. They just love to make up a huge campaign and then spring it on someone 3 days before go-live that they need a whole ton of changes made and promoted. So they outsource it all to 3rd party contractors who fucked everything up so badly that the site (which uses a hugemoney mega-CMS specifically so we could fucking have marketing do the copy edits in-house) is now practically only maintainable by more contractors. Who just make it worse with each iteration.
Finally someone got fed up with it... so now I get the whole fucking thing dumped in my lap. Except they still want the contractors doing shit. So I just get shat on.
-
Yes.
Sort of.
Some things take for fucking ever and it doesn't make much sense why.Also, if you do tabbed/multi-window browsing, somewhere around 4 or 5 tabs Dicsourse started shitting itself with too many polling routines.
-
@Intercourse said:
Is it normal for so many JSON POST methods to just hang for 15s at a time? Every one of them is 15.08s and 241B.
and just wait til you start getting intermittent 500 errors
-
and just wait til you start getting intermittent 500 errors
Meh, I have been getting those for a while.
-
Also, if you do tabbed/multi-window browsing, somewhere around 4 or 5 tabs Dicsourse started shitting itself with too many polling routines.
This machine only has a quad core and 16GB of RAM. I am not sure it could handle that many Discourse tabs.
I can run 3-4 VMs at a time as long as they do not hit the i/o too much, but that much Discourse might cause it to smoke.
-
Wonder if it's possible to poison discourse editor by using a browser that doesn't support utf8 (ie, one of the bots we have running around)
Or post content. I have not been hitting this issue lately but I've also been avoiding the likes thread and other crazy fast threads.
-
-
I expanded a template so I can figure out what particular piece of data is causing this, it was appending 5 strings originally so very hard to figure out which one is poison
-
I expanded a template so I can figure out what particular piece of data is causing this, it was appending 5 strings originally so very hard to figure out which one is poison
That this is true at all is just abysmal. It's one of the worst features of Ruby. Or maybe it's a bad feature of RoR which messes up how string concatenation works.
Protip to anyone writing string concatenation code: normalize to one of the Unicode formats first. Anything else is just hell. (It doesn't really matter which you pick so long as you choose just one of them.)