Not receiving e-mail notifications
-
At the time I'm writing this, it's been 11 hours since I received the last notification from Discourse. CS notifications are arriving without problems.
-
Confirmed. Nothing showing in the logs as changed, so dunno what needs looking at.
Test message sent from settings page, but not received (at least not immediately.)
-
-
Test e-mail?
-
The job queue is being flooded by a bot....
-
You said @PaulaBean. Is it front page comment page volume?
-
-
I can see huge amount of load via calls to
/t/656.json /t/769.json
and so on and so on in a massive flood. nginx logs are not that happy now. and since these are validated API calls performed on behalf of admin a lot of throttles are not kicking in.
I am considering adding some built-in DoS protection to the nginx config.
Its clearly a bug cc @apapadimoulis
-
In other news, it seems that Ruby is actually holding up quite well here, considering.
-
Hmm ... are these calls to read the comments?
These shouldn't happen all that often...
-
Yeah, its still totally flooding. See this:
cd /var/docker ./launcher ssh app cd /var/logs/nginx tail -f access.log
Going to change the base nginx template to protect itself, but the bot is still rogue, add a throttle to ensure it never calls an endpoint more than say once every 30 secs.
-
-
All of this bagging of Ruby's shitty perf, and here we are on a virtual host, DoSing ourselves and stuff is still working.
-
All of this bagging of Ruby's shitty perf, and here we are on a virtual host, DoSing ourselves and stuff is still working.
I've never used Ruby (its syntax is a major turnoff to me). I only know what I've read about it. And even The Blog That Shall Not Be Linked was griping about performance, in the very same post that was trying to persuade me to try it.
Ruby is a decent performer, but you really need to throw fast hardware at it for good performance. Yeah, I know, interpreted languages are what they are, and caching, database, network, blah blah blah. Still, we obtained the absolute fastest CPUs you could buy for the Discourse servers, 4.0 Ghz Ivy Bridge Xeons, and performance is just … good on today's fastest hardware. Not great. Good.
-
I find that for web apps, in general, the server bottleneck is the DB. Do DB work right that is the first and most important job you have.
Now, Go would be a lot faster than Ruby, no argument there. But PHP/Python vs Ruby are all pretty similar in terms of perf.
-
Now, Go would be a lot faster than Ruby, no argument there. But PHP/Python vs Ruby are all pretty similar in terms of perf.
Are you @ben_lubar in disguise??
-
Go would be a lot faster than Ruby
No trouble at all guessing which one user liked @sam's post.
-
And here I was thinking nobody loved me any more.
-
Going to change the base nginx template to protect itself, but the bot is still rogue, add a throttle to ensure it never calls an endpoint more than say once every 30 secs.
FYI - going to take a stab at this tomorrow. The TDWTF change was a hack on top of a hack on top of a pile of hacks on top of a bunch of ASPX pages.
-
-
-
Poor sad Keanu.
-
He should have a box of chocolates.
-
Email notifications should be back now.
-
Email notifications should be back now.
Just seen a couple go out to @ender and @Lorne_Kates ...
-
note, message bus was reset with redis, meaning everyone should refresh browsers for stuff to go back to normal notification wise.
-
-
What the hell is that abomination? o.O
Clearly it is an icon with 3 people represented by grey blobs. Duh.
-
I'm gonna assume it's the result of this:
http://what.thedailywtf.com/t/how-do-you-know-if-your-forum-software-is-trwtf/827/14?u=onyx
It does not excuse the horrible icons though.
-
What the hell is that abomination?
Oh my!
I'm gonna assume it's the result of this:
http://what.thedailywtf.com/t/how-do-you-know-if-your-forum-software-is-trwtf/827/14Looks like it...
@Sam - is that configurable?
Oh. Look. Another bug. Oneboxed posts with lists in them, don't render the lists...
-
Not a bug -- all quotes, including oneboxes, do not render formatting (with the exception of hyperlinks). At least, they were never intended to, and have not since we started the project.
-
-