Cooties
-
500 Not OK
-
Pass. I've not been doing anything - haven't even been on the site.
-
-
-
Thanks Discourse, it's not like I needed that profile menu, you can keep it.
-
Thanks Discourse, it's not like I needed that profile menu, you can keep it.
-
I've been getting a ton of 500s....
-
And it appears some people are posting their messages twice just to be sure
-
Nginx seems to be refusing some connections???
Filed under: Sorry an error has occurred, 502 Ok
-
And it appears some people are posting their messages twice
just to be surebecause this fucking piece of shit software pretended it didn't save at first
-
Nginx seems to be refusing some connections???
I've tried rebooting the container.
-
How about just giving it the boot?
-
Worthless piece of garbage. Why is anyone paying Atwood for this monstrosity that dares to call itself a forum?
-
Did anyone else get a self emptying notifications list just before the cooties?
-
I did!
-
-
Did anyone else get a self emptying notifications list just before the cooties?
I'm not sure about before, but definitely during.
-
Did anyone else get a self emptying notifications list just before the cooties?
Yes. Presumably the notifications get emptied alongside Discourse's bowels.
-
That was just the first hiccup it seems:
16:25 in my screenshot is likely when @pjh reset the container.
-
-
My God, it's in v-fib!
No, it's Discourse, that just means it's running. Or servercooties' scoring metric is off.
-
The 500 errors are spreading....
https://meta.discourse.org/t/500-internal-server-error-when-trying-to-write-a-new-topic/37026
-
Deja vu, even the likes are equal. And Discourse didn't notice the bodies being too similar?
-
..... what just happened?
I got a 500 error, so I went in and deleted the failed backup.
-
Is broked again:
-
Hi!
-
So - I moved
places of worshippub and while I did...Me, on this crappy laptop, using others' WiFi cannot be the sole cause of cooties - since it started hours after my first place of worship...
NFC what's going on.
-
.... what?
where?!
.....
/me mutters and writes down a note to find and delete that offending JS
-
That's how I expect a website called WTF to behave
-
So if the actual database is only 15GB, how are we filling up nearly 60GB of space?
bastards
-
The 500 errors are spreading....
https://meta.discourse.org/t/500-internal-server-error-when-trying-to-write-a-new-topic/37026
I like this quote:
Seems like it works from time to time anyway, but I can't figure out when.
-
-
/me mutters and writes down a note to find and delete that offending JS
Deja vu...
NedFodder's refreshed in the past six months, right?
-
There she blows!
NaN == NaN false EmberSucks true
-
Before today's
backupcrash that I have to clean up after every day, can you disable the automated backup in the admin panel? The hard drive isn't going to be getting less full.
-
servercooties' scoring metric
That one stumps me, by the way - @accalia, how do you calculate the apdex? It seems like it jumps between 0, 50 and 100% arbitrarily... too high resolution, perhaps? Shouldn't you be using some longer rolling window?
-
I have tried to post on WTDWTF today on 4 separate occasions and this is the frist one that I didn't get a 500 OKAY, ELGIU YOU on.
-
etclroanwjuaoneoansmeuonsoethmeo.seoame.oans
EDIT: Hooray, looks like after a storm of 500 errors Discourse unfucked itself...
-
-
Only temporarily, I'm sure.
OK, let me rephrase that...
Discourse
unfucked itselfhas returned to the regular state of fuckery.
-
That one stumps me, by the way - @accalia, how do you calculate the apdex?
for the endpoint measurements? 100% is < 3 second response, 50% is > 3 seconds but < 12 seconds, 0 is > 12 seconds
overall is the average of the last three checks for each endpoint.
it's not the best algorithm... I keep meaning to find some sort of poly curve that fits a nice progression (basically fitting the defined points in a neat way) and interpolating in between values, then dropping overall to a simple average of latest check on each endpoint.
-
root@what:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/vda1 61796348 58570972 63264 100% /
none 4 0 4 0% /sys/fs/cgroup
udev 2013288 8 2013280 1% /dev
tmpfs 404832 340 404492 1% /run
none 5120 0 5120 0% /run/lock
none 2024140 512 2023628 1% /run/shm
none 102400 0 102400 0% /run/user
root@what:~# ls /var/discourse/shared/standalone/backups/{,default/}
/var/discourse/shared/standalone/backups/:
default/var/discourse/shared/standalone/backups/default/:
-
Discourse
unfucked itselfhas returned to the regular state of fuckery.Well, that didn't last long. I wonder how many tries it will take to post this...
A few tries at ~10 second intervals, backing off to 30 seconds. 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32 ... and at this point, screw it; I'll do something else for a while and come back when servercooties shows something besides flatline.
-
Well shit...
-
I clicked this, the Cooties topic, and...
Natch.
-
root@what:~# du -s /var/lib/docker
34178240 /var/lib/docker
root@what:~# du -s /var/discourse/shared/standalone
37164992 /var/discourse/shared/standaloneSo, something huge is inside Docker. @PJH, what do we do?
root@what:~# docker images -a REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE local_discourse/app latest 1f19af41e12e 10 weeks ago 1.932 GB samsaffron/discourse 1.0.13 27f52292c186 3 months ago 1.238 GB <none> <none> 157f6a775410 3 months ago 1.238 GB <none> <none> 7ea991d02f7e 3 months ago 1.238 GB <none> <none> 65746d67224e 3 months ago 1.238 GB <none> <none> dd46ba35af06 3 months ago 821.1 MB <none> <none> d3a1f33e8a5a 4 months ago 188.2 MB root@what:~# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 899929e6af7a local_discourse/app:latest "/sbin/boot" 10 weeks ago Up 4 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp app
root@what:/# du --max-depth=1 /var/www/discourse/tmp/backups/default/ 3720040 /var/www/discourse/tmp/backups/default/2015-12-19-042932 3722508 /var/www/discourse/tmp/backups/default/2015-12-20-035253 7282576 /var/www/discourse/tmp/backups/default/2015-12-22-044854 14725128 /var/www/discourse/tmp/backups/default/ root@what:/# rm -r /var/www/discourse/tmp/backups/default/* root@what:/# df Filesystem 1K-blocks Used Available Use% Mounted on rootfs 61796348 43371776 15262460 74% / none 61796348 43371776 15262460 74% / tmpfs 2024140 0 2024140 0% /dev shm 65536 0 65536 0% /dev/shm /dev/disk/by-label/DOROOT 61796348 43371776 15262460 74% /shared tmpfs 2024140 0 2024140 0% /proc/kcore
-
Also:
It (was?) dead, Jim.
-
NOTE TO PEOPLE DESIGNING A SYSTEM: maybe don't store temporary data outside of the system temporary folder? Or at least delete it if whatever action you're doing with it fails?
-
-
Only temporarily, I'm sure.
Of course it's temporary! It repeats, going back and forth, sometimes rapidly, sometimes slowly, but never stopping!