Moar Cooties
-
Hmmm... I'll have to try "System"....
Filed Under: What could go wrong with that?
-
've not personally been on site since about 22:00 CST on 22-NOV...Do I have something in my profile causing "Disco-Quakes" on the server?
That time frame would match the logs in question, which were for:
Analyzed: /var/log/nginx/access.log,/var/log/nginx/access.log.1 on what.thedailywtf.com-app Limited to 2015-11-21T19:00:54+00:00 - 2015-11-22T19:00:54+00:00 ---------------------------------------------------------------------------------------------------- 22/Nov/2015:07:35:34 +0000 - 22/Nov/2015:07:35:33 +0000
You were still the top non-anonymous user the next disco day:
Top 30 users by Server Load Username Duration Reqs Routes -------- -------- ---- ------ [Anonymous] 161680.44 85698 -(59829.13) topics/show(36521.73) - (POST)(32313.58) user_avatars/show(19365.94) list/latest(2897.49) M_Adams 93852.09 4013 users/show(76030.53) topics/timings (POST)(13669.63) user_avatars/show(2812.87) clicks/track(516.32) posts/markdown_num(345.67)
-
I tried to read the mafia a 3 times but I got jellied down... Jesus Christ it's annoying...
-
I need to "mea culpa" on this one after doing some digging...
-
-
What's the latest top users/pages info?
-
yep.... that's some fine cooties.,..
anything in the logs that might help?
in particular has @zoidberg and @sockbot dropped at all in their resource utilization? <div
-
@accalia has summoned me, and so I appear.
-
Doctor Zoidberg, soaking in brine.
-
What's the latest top users/pages info?
That's a daily thing. Next one is scheduled to drop in less than an hour, but it captures data from 07:35 to 07:35 UTC, so we'll have to wait for tomorrow's report to see if there's anything interesting in there.
-
Next one is scheduled to drop in less than an hour, but it captures data from 07:35 to 07:35 UTC
..... what the actual fuck?!
seriously?!
-
From the most recent report (about 10 minutes ago):
Analyzed: /var/log/nginx/access.log,/var/log/nginx/access.log.1 on what.thedailywtf.com-app Limited to 2015-12-06T18:51:14+00:00 - 2015-12-07T18:51:14+00:00 ---------------------------------------------------------------------------------------------------- 07/Dec/2015:07:35:29 +0000 - 07/Dec/2015:07:35:29 +0000
-
Also - what are our numbers here, out of curiosity?
-
-
Five 5xx errors?! I've had more than that in the last 10 minutes
-
The 5xx counter is a lie
-
They probably sweep their crashes under 4xx so that if anyone calls them out on that, they can say "oh, you must have a lot of dead links somewhere, everybody's 404ing!"
-
Ouch
-
I think I have some deleted things to cause 404 on my own site
-
Or roll 5xx into 2xx OK. Or something else Discological.
-
-
They probably sweep their crashes under 4xx so that if anyone calls them out on that, they can say "oh, you must have a lot of dead links somewhere, everybody's 404ing!"
I suspect that most of the 5xx errors come from nginx. The ruby part of the server never knows about them and doesn't count them.
-
I found this ironically amusing:
-
This post is deleted!
-
What I hate about that try again button is that it's kind of a lie. It will try again. But if it loads, you end up at the top of the thread, even though the URL says you should be somewhere else.
Then anytime to come back to that thread in the current session you get the try again page before the actual page loads (assuming no additional error, of course).
-
@PJH are you doing something in your import script testing that could cause this?
-
He's not importing from here, he's importing from a backup on one of his own machines.
-
Given neither server my testing is happening on is the one the site is running on, no.
I've just rebooted this one and stuff seems to have calmed down a bit:
-
What I hate about that try again button
Meh, I just use this button:
Unfortunately, in Discourse I have to use it probably more often than all other websites combined.
-
From the most recent report (about 10 minutes ago):
Analyzed: /var/log/nginx/access.log,/var/log/nginx/access.log.1 on what.thedailywtf.com-app Limited to 2015-12-06T18:51:14+00:00 - 2015-12-07T18:51:14+00:00 ---------------------------------------------------------------------------------------------------- 07/Dec/2015:07:35:29 +0000 - 07/Dec/2015:07:35:29 +0000 ```</blockquote> ..... discourse makes no sense anymore......
-
From the most recent report (about 10 minutes ago):
Analyzed: /var/log/nginx/access.log,/var/log/nginx/access.log.1 on what.thedailywtf.com-app Limited to 2015-12-06T18:51:14+00:00 - 2015-12-07T18:51:14+00:00 ---------------------------------------------------------------------------------------------------- 07/Dec/2015:07:35:29 +0000 - 07/Dec/2015:07:35:29 +0000 ```</blockquote> ..... discourse makes no sense anymore......<div
-
-
I've no idea what's going on. Just restarted the container.
-
-
Can't you just make this a
yearlymonthlydaily task? I mean, we are pretty used to the forum going down for a bit anyway. So - personally - I'd rather take a known downtime on a certain timeframe than having to hope that502 OK
doesn't haunt me.
-
Sounds like a work for ITAPPMONROBOT
-
certain statements
Such as 1E615951597716083A1E884F2BCACD6E ? Or maybe just 1104C54A9EC6549E4EF9562B687596FB. That should fix it.
-
Since this is Discourse we are talking about, I was thinking more of
_*)Filed Under: Which only looks close to yours on the outside
-
Or make it a and let servercooties.com send an email to the WTDTF server everytime it gets some "bad" result. That email is parsed for certain statements which trigger the reset of the container / server / universe
Taking you seriously for just one moment - I'll be the first one to say that I wouldn't trust servercooties code that much. Now, this is not a slam against anyone who worked on it (I didn't even touch the backend pretty much) it's just... well, we hacked this thing together in our spare time for shits and giggles, I'm not sure if it's really "production ready".
Then again, we probably have better testing in place than Discourse...
-
Then again, we probably have better testing in place than Discourse...
No one was banned from your dev / testing topics AFAIK.
-
@Onyx said:
Then again, we probably have better testing in place than Discourse...
No one was banned from your dev / testing topics AFAIK.
Yet.
-
/kick #servercooties @loopback0 "for being a smartarse"
-
No one was banned from your dev / testing topics AFAIK.
Testing was not rigorous enough.
-
-
I don't see anything terribly egregious in the latest logs.
-
I prefer Ctrl+F5 :P
-
Ctrl+Shift+R because it's the same whether I use a Chromebook or a Windows keyboard. Because Chromebooks do not have function keys:
(They do, but they are repurposed)
-
It doesn't catch any of the nginx generated ones like 504 because, well, by their nature it doesn't know about them (because that means discourse failed to reply properly/at all)
Technically the 504s are "client side" errors to discourse, but in the reverse proxy model they're server side, hence 5xx
-
-
Hmmm....are the bots reading /t/1000 again?
Top 30 users by Server Load Username Duration Reqs Routes -------- -------- ---- ------ [Anonymous] 67467.28 91071 topics/show(27450.96) - (POST)(14516.09) -(8825.19) user_avatars/show(8058.52) list/latest(2724.26) CodingHorrorBot 10422.46 5430 topics/show(6887.18) posts/show(2354.69) topics/posts(956.11) notifications/index(156.41) notifications/mark_read(68.07) discoursebot 10041.30 5428 topics/show(6585.73) posts/show(2124.56) topics/posts(1089.89) notifications/index(178.66) notifications/mark_read(62.47) Zoidberg 7816.81 5180 topics/show(4335.89) posts/show(1838.62) topics/posts(1183.06) list/latest(205.81) notifications/index(174.25) RPBot 7637.62 5161 topics/show(4178.35) posts/show(1658.23) topics/posts(1502.28) list/latest(139.14) notifications/index(88.99) sockbot 7344.31 4509 topics/show(4489.71) posts/show(1713.20) topics/posts(709.72) notifications/mark_read(163.80) notifications/index(131.40) MathBot 6964.07 4872 topics/show(4091.55) posts/show(1604.77) topics/posts(976.63) notifications/index(115.81) list/latest(98.47) NetBot 6499.11 4743 topics/show(3765.16) posts/show(1405.50) topics/posts(1055.21) notifications/index(146.57) list/latest(69.02) ... Top 30 urls by Server Load Url Duration Reqs --- -------- ---- GET /t/1000.json?include_raw=1&track_visit=true HTTP/1.1 39750.54 11599 POST /topics/timings HTTP/1.1 27310.29 44956