Post AQW8RCDLHWtT2YrZMe by p@freespeechextremist.com
(DIR) More posts by p@freespeechextremist.com
(DIR) Post #AQP7y5OkBWE1Ocb0V6 by shitpisscum@social.mrhands.horse
2022-12-08T17:54:27.996581Z
4 likes, 1 repeats
@p @sjw Hi, sorry for spamming, any of y'all know how to clear oban queue (or whatever it's called) in Pleroma OTP builds?CC @coyote in case this ends up improving anything
(DIR) Post #AQSquARWZ5jVIOHWts by p@freespeechextremist.com
2022-12-10T13:02:08.120315Z
5 likes, 1 repeats
@shitpisscum @coyote @sjw Clear it completely? You probably don't want to do that, but you can, just `truncate oban_jobs;`. Don't do that, though. Just do something like `delete from oban_jobs where attempt >= 3;` or something. They're both basically hatchet jobs you only want to do if there's an emergency but the latter is slightly less stupid.
(DIR) Post #AQSqyhUPdm0awinIum by p@freespeechextremist.com
2022-12-10T13:02:57.262784Z
3 likes, 1 repeats
@shitpisscum @coyote @sjw Or I've done this before when Poast's job queue was clogged up: `update oban_jobs set max_attempts = 3;`. Then there's no disrupting the flow.
(DIR) Post #AQSsQxVzkeJsi8ZaIi by shitpisscum@social.mrhands.horse
2022-12-10T13:19:14.781178Z
1 likes, 0 repeats
@p @sjw @coyote Fuck I already deleted everything in the meantime. Didn't really change anything btw, still the same failure mode: CPU locked at 100% for a few hours before crashing, posting and outgoing federation seems to be kind of working (I managed to get pigpoopballsbot posting lol), you might even manage to load known network if you're lucky. One more interesting thing I discovered thanks to my lazyness: if I start Pleroma without disabling iptables (long story but it basically blocks all incoming connections by default) it appears to be working so maybe it's getting to much shit incoming.Any other idea what I could attempt to bring it back up? I remember you talking about rate limiting incoming federation, how exactly do you do that?
(DIR) Post #AQSsj2n6sF5YHqCa6y by shitpisscum@social.mrhands.horse
2022-12-10T13:22:31.019965Z
1 likes, 0 repeats
@p @coyote @sjw also>They're both basically hatchet jobs you only want to do if there's an emergency I think this can qualify as an emergency lol
(DIR) Post #AQTDxZ4Nl2SPUM2vHk by p@freespeechextremist.com
2022-12-10T17:20:27.884946Z
2 likes, 0 repeats
@shitpisscum @coyote @sjw > if I start Pleroma without disabling iptables (long story but it basically blocks all incoming connections by default)iptables doesn't do that, just your distro is shit. It's built into the kernel, it's not a service really.> maybe it's getting to much shit incoming.If you're down for any length of time, it will do that. You can usually just ride out the errors but sometimes it takes a day or two.> I remember you talking about rate limiting incoming federation, how exactly do you do that?The short version is you put something like this at the top level:limit_req_zone $binary_remote_addr zone=makeUPaZONEname:20m rate=40r/s;Then in the location block:limit_req zone=theZONEnameYOUmadeUP burst=100;limit_req_status 429;The docs for limit_req_zone, limit_req, and limit_req_status should give you most of what you want to know.
(DIR) Post #AQTEsVNa9PHOY8B6Ia by shitpisscum@social.mrhands.horse
2022-12-10T17:30:44.084332Z
3 likes, 0 repeats
@p @sjw @coyote That's Nginx config? I assumed I'd have to fuck with Pleroma config, I'll check it out. Thanks. Also>your distro is shitit's a compute instance on Oracle cloud so yea I guess...
(DIR) Post #AQTO715pw4BeY8s8ie by p@freespeechextremist.com
2022-12-10T19:14:13.388584Z
2 likes, 0 repeats
@shitpisscum @coyote @sjw You don't have to do anything with Pleroma there, just put it into whatever location block applies to /inbox, make one if it doesn't exist. Those limits are pretty generous for just POSTing to /inbox. You can figure out something reasonable by looking at your logs and seeing what's going on when your server breaks, and that helps establish the boundaries, "This kind of traffic and above breaks the shit".
(DIR) Post #AQTPEJEYzFm8nFzlku by coyote@pl.lain.sh
2022-12-10T19:26:30.103171Z
1 likes, 0 repeats
@p @sjw @shitpisscum he may wanna think about clearing old remote postshe can use this command after setting the remote limit (you’ll lose old favorites, convos, and bookmarks) sudo -Hu pleroma MIX_ENV=prod mix pleroma.database prune_objects --vacuum
(DIR) Post #AQTPHHOsGFLvyWEbNA by coyote@pl.lain.sh
2022-12-10T19:27:14.361219Z
1 likes, 0 repeats
@p @shitpisscum @sjw I set it to 60 just because I wasn't sure, but it'd probably be better at 90 but lower than 9 months
(DIR) Post #AQTRovC3X0dgr9PNMe by shitpisscum@social.mrhands.horse
2022-12-10T19:55:45.263277Z
3 likes, 0 repeats
@p @sjw @coyote >put it into whatever location block applies to /inboxDumb question, that's inside the server block for shitpisscum.mooo.com (/etc/nginx/sites-available/shitpisscum.mooo.com) right? Just add something like:limit_req_zone $binary_remote_addr zone=cum:20m rate=40r/s;location /inbox{limit_req zone=cum burst=100;limit_req_status 429;}Also just had a better look at my access.log, what the fuck happened here?
(DIR) Post #AQTS4I8oUjIkN4Dk7U by coyote@pl.lain.sh
2022-12-10T19:58:27.434243Z
2 likes, 0 repeats
@shitpisscum @sjw @p yeah that nginx is proper
(DIR) Post #AQTSCQY57SyulNv2Tg by shitpisscum@social.mrhands.horse
2022-12-10T20:00:00.226207Z
3 likes, 3 repeats
@p @coyote @sjw Here's one from a bit earlier (let's not talk about cum.salon user agent for now)
(DIR) Post #AQTSEaVZ3saYENlv9s by shitpisscum@social.mrhands.horse
2022-12-10T20:00:24.250251Z
1 likes, 0 repeats
@coyote @sjw @p Ok lemme try add that then
(DIR) Post #AQTSLXWsXEjT1GhYXo by coyote@pl.lain.sh
2022-12-10T20:01:22.432474Z
2 likes, 0 repeats
@shitpisscum @sjw @p first screenshot: I think social.linux.pizza is sending you statuses/activitiessecond screenshot: 500 errors to social.linux.pizza (your server shat itself? idk...)third screenshot: more 500 bad gateway errors from your machine to other servers, see the big "502" ? that means "bad gateway" while they were trying to send you statuses
(DIR) Post #AQTSrIswW7KKrtATnk by shitpisscum@social.mrhands.horse
2022-12-10T20:07:23.459934Z
0 likes, 0 repeats
@coyote @sjw @p >social.linux.pizza is sending you statuses/activitiesYea I thougnt maybe that "burst" of statuses from them had something to do with the server shitting itself, I'll wacth the logs if/when it crashes again (eventually pigpoopballsbot tried to post so the rest of the access.log is pretty much useless lol (don't put try/except inside while true loops kids (unless you want something like this)))
(DIR) Post #AQTUzWkD4ZRw4o8GMC by shitpisscum@social.mrhands.horse
2022-12-10T20:31:17.134421Z
2 likes, 0 repeats
@coyote @p @sjw Ok running now, let's see for how long
(DIR) Post #AQUEt56bW3PsVhTI3M by p@freespeechextremist.com
2022-12-11T05:05:34.251228Z
1 likes, 0 repeats
@coyote @shitpisscum @sjw This completely fucks bookmarks and other things.
(DIR) Post #AQUEzPxet6m4vlJCAi by coyote@pl.lain.sh
2022-12-11T05:06:33.621989Z
1 likes, 0 repeats
@p @sjw @shitpisscum yeah :/ last resort for sure
(DIR) Post #AQUFFUxS4u0d3psblg by sjw@bae.st
2022-12-11T05:09:35.275408Z
2 likes, 0 repeats
@shitpisscum @p @coyote DELETE FROM ONLY oban_jobs;
(DIR) Post #AQUH40LNlAZeptihwO by p@freespeechextremist.com
2022-12-11T05:29:57.300604Z
2 likes, 0 repeats
@shitpisscum @coyote @sjw > configYeah, all accurate except two things. The limit_req_zone declaration has to go at the top level, and in the block, you'll also need to direct it to Pleroma as the upstream.> Also just had a better look at my access.log, what the fuck happened here? Looks like a lot of posts are getting delivered. They're probably mostly retries that have accumulated while it was down. That has happened to FSE, and you just ride it out.
(DIR) Post #AQUkHJKbNEEs9y3IVk by coyote@pl.lain.sh
2022-12-11T10:57:08.937248Z
2 likes, 0 repeats
@p @sjw @shitpisscum pee could I bug you about db timeouts? I'm getting a lot of them, 200-400ms though, not enough that it should give up so quick, pleroma won't even load profiles... any ideas?
(DIR) Post #AQUkapy8Fgousxqx7I by shitpisscum@social.mrhands.horse
2022-12-11T11:00:49.613297Z
1 likes, 0 repeats
@p @sjw @coyote >and in the block, you'll also need to direct it to Pleroma as the upstreamHow do I do that?
(DIR) Post #AQUlNPigdO8vfHn9DE by shitpisscum@social.mrhands.horse
2022-12-11T11:09:35.685466Z
1 likes, 0 repeats
@sjw @p @coyote Already did that (spoiler alert it didn't help)
(DIR) Post #AQUmODhatv12dXEG8G by shitpisscum@social.mrhands.horse
2022-12-11T11:20:56.733923Z
1 likes, 0 repeats
@p @coyote @sjw Like this?
(DIR) Post #AQUnNOOFmGHNRwLs5Q by shitpisscum@social.mrhands.horse
2022-12-11T11:32:00.079782Z
1 likes, 0 repeats
@coyote @p @sjw Ok running again and returning 200s
(DIR) Post #AQVrKkdxB5rwZZeRjU by p@freespeechextremist.com
2022-12-11T23:51:04.418981Z
1 likes, 0 repeats
@coyote @shitpisscum @sjw Is it timeouts getting a connection?
(DIR) Post #AQVrPk4uhs2MGfdq9g by p@freespeechextremist.com
2022-12-11T23:51:58.536845Z
2 likes, 0 repeats
@shitpisscum @coyote @sjw Same way you do it elsewhere, with proxy_pass.
(DIR) Post #AQVrYkCJdFVnFDOdA8 by shitpisscum@social.mrhands.horse
2022-12-11T23:53:35.384301Z
1 likes, 0 repeats
@p @sjw @coyote Yea I figured it out in the meantime
(DIR) Post #AQVrsmUKpDts8lNYgK by coyote@pl.lain.sh
2022-12-11T23:57:10.295736Z
1 likes, 0 repeats
@p @sjw @shitpisscum yeah connection between pleroma and postgresql
(DIR) Post #AQVs72OYTsXBWpTQP2 by shitpisscum@social.mrhands.horse
2022-12-11T23:59:47.525284Z
1 likes, 0 repeats
@coyote @sjw @p That's pretty much considered normal with Pleroma lol
(DIR) Post #AQVu2Nl3pHtQFFuNDk by p@freespeechextremist.com
2022-12-12T00:21:22.137403Z
0 likes, 0 repeats
@coyote @shitpisscum @sjw Getting a connection versus timeouts on the query versus timeouts connecting to the DB, it's three different problems.
(DIR) Post #AQVyl0UjZ65OwWo19U by coyote@pl.lain.sh
2022-12-12T01:14:12.320696Z
2 likes, 0 repeats
@p @sjw @shitpisscum Sorry, I'll check.
(DIR) Post #AQW2iHUWJceGbYf4a0 by p@freespeechextremist.com
2022-12-12T01:58:34.878267Z
7 likes, 4 repeats
@coyote @shitpisscum @sjw No worries, man. It's probably the first one on the list. Lemme just do a huge-ass post dumping all my thoughts about the recent uptick in problems.So, here's how this all works: there is a pool of connections, recycled between various pieces of Pleroma. So to talk to the DB, a thread in Pleroma requests a connection from the pool, then that connection is "checked out" and when it's done, it's returned to the pool. That process can time out: if you have 10 connections in the pool and 10 workers working with something and they all have the connections checked out, then an 11th worker will wait a small amount of time for one of them to finish and the connection to become available. Establishing a connection (i.e., filling the pool by adding connections) can also time out. Queries can also time out: if you have an active query that's taking too long.The thing I keep saying about dnsmasq being useful because connections are checked out while the domain name is resolved? It is intended to reduce time being spent with a connection checked out, which prevents other processes from timing out. I think the default wait for a connection from the pool is 100ms or 150 or something (FSE has it set to 800ms), so you can see that if it takes 50ms to resolve a domain vs. taking 2ms, that's a lot of overhead eliminated, it stops workers timing out.This is also why I keep asking people what the active queries are. (`select state,pid,CURRENT_TIMESTAMP-query_start, datname, query from pg_stat_activity where state <> 'idle' order by CURRENT_TIMESTAMP-query_start DESC;`) If a connection is checked out because there's some ridiculous long-running query, then figuring out what that query is means the bottleneck is easy to find. But you've got to run it while the errors are happening, that data is mostly useful in aggregate.So, Pleroma's default config also uses a lot of disk I/O. Postgres also does. So if there are four or five Postgres workers doing heavy I/O on the same disk as four or five Pleroma workers, you're thrashing pretty hard at that point. This is one of the over 9,000 reasons that FSE does not process media files: we don't proxy any of them, we don't scrub them, we don't alter them, we don't generate thumbnails, etc. Pleroma does very little disk I/O on FSE, only on uploads, and it's using a different disk than Postgres so it doesn't interfere even if we were I/O-heavy.Apparently a lot of people are not serving static content through nginx. It is balls-ass slow to serve it through Elixir. nginx lets you add backend timing metrics so that you can see what's slow. In addition to that, it lets you turn the timestamp into something easier to parse, and if you use tabs, then it's a TSV that you can pipe into awk or R or Ruby or Python or whatever you use to process TSVs. Here's my log format, these lines go into the top-level "http {" block::mycomputer: log_format urrthang '$remote_addr $remote_user [$time_iso8601] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent" $request_time $upstream_connect_time $upstream_header_time $upstream_response_time $server_name $http_x_forwarded_for';:mycomputer: access_log /var/log/nginx/access.log urrthang;Keep in mind that those are tabs rather than spaces and the *location* of the log file might be different for your OS/distro combination. Once I have that, I can tail the logs and do things like check how often a given backend-involved endpoint is hit::mycomputer: tail -f -n 900001 /var/log/nginx/access.log | mawk -Winteractive -F"\t" '$11!="-"{split($4, a, / /); r = a[1] " " a[2]; count[r]++; print count[r], $1, r}'Or print out averages of the $upstream_header_time field by endpoint. (Where $upstream_header_time, the 11th field, is "-", nginx didn't send the req upstream.)Everyone having these problems with Pleroma seems to be on 2.4.3 or 2.4.4. Commit fa3157df964d4f88d0fd1ce466a44333c8c7ef60 makes authenticated connections bypass the cache. That will affect performance, that might be what is stressing the DB. A big-ass pipeline for timelines got bigger, it looks like it had to do with filtering reposts of muted users' statuses and things like that, that's going to affect performance. I don't know what's causing all these problems but I think people should try downgrading to 2.4.2 and if that solves it, file a bug on git.pleroma.social.
(DIR) Post #AQW3cSbiAowFIToUqm by coyote@pl.lain.sh
2022-12-12T02:08:29.996971Z
2 likes, 0 repeats
@p @sjw @shitpisscum it looks like I'm having trouble establishing a connection to the pool, should I send a brief log?
(DIR) Post #AQW3hkNBY4D7qPXWkK by coyote@pl.lain.sh
2022-12-12T02:09:37.022507Z
2 likes, 0 repeats
@p @shitpisscum @sjw Honestly I'm having trouble telling exactly if that's the issue
(DIR) Post #AQW4dXdj33Oh9HppTM by Cumsocks@freecumextremist.com
2022-12-12T02:20:06.416242Z
2 likes, 2 repeats
@p @sjw @coyote @shitpisscum gonna squeeze myself into the thread. probably won't be of help but trying to understand and keep track of this
(DIR) Post #AQW54ideGNX74zl3my by hakui@tuusin.misono-ya.info
2022-12-12T02:25:01.442819Z
8 likes, 1 repeats
@p @coyote @shitpisscum @sjw >Everyone having these problems with Pleroma seems to be on 2.4.3 or 2.4.4.tfw 2.1.2 :smug1:
(DIR) Post #AQW5GGnfaiz4DPxAoa by coyote@pl.lain.sh
2022-12-12T02:26:55.446759Z
2 likes, 0 repeats
@hakui @sjw @p @shitpisscum suya..
(DIR) Post #AQW5HUoKz8fxxUqmPI by hakui@tuusin.misono-ya.info
2022-12-12T02:27:20.153104Z
3 likes, 0 repeats
@coyote @p @shitpisscum @sjw :suya:
(DIR) Post #AQW8RCDLHWtT2YrZMe by p@freespeechextremist.com
2022-12-12T03:02:43.423147Z
2 likes, 0 repeats
@coyote @shitpisscum @sjw Think it's getting an available connection from the pool, but try running `psql` to see if you can connect.
(DIR) Post #AQWBIB1icwYoc6ojBI by p@freespeechextremist.com
2022-12-12T03:34:42.529423Z
5 likes, 1 repeats
@hakui @coyote @shitpisscum @sjw FSE's 2.2.2. :smug2:
(DIR) Post #AQWBb7OgLWV0rIadxw by hakui@tuusin.misono-ya.info
2022-12-12T03:38:06.650937Z
3 likes, 1 repeats
@p @coyote @shitpisscum @sjwa12012c645344971783e685c3f0b92a…
(DIR) Post #AQWC1595L8enP9fvBA by ins0mniak@cyberstorm.one
2022-12-12T03:42:32.305959Z
3 likes, 0 repeats
@p @sjw @coyote @shitpisscum @hakui Yo P did you get chance to check out @cyotote@pl.lain.sh 's show last week?The bro really rocked out. Dude he played some really dope music. I was sick with covid, but man it rocked.
(DIR) Post #AQWDoLXjGN2aP8G0H2 by p@freespeechextremist.com
2022-12-12T04:02:55.964745Z
4 likes, 0 repeats
@ins0mniak @coyote @hakui @shitpisscum @sjw I did not. I was two hours early to it, then I ended up getting stuck on something, I forget. I was sad to have missed it.
(DIR) Post #AQWEDQz8APugWQ2LNA by ins0mniak@cyberstorm.one
2022-12-12T04:06:46.161453Z
3 likes, 0 repeats
@p @sjw @coyote @shitpisscum @hakui Yeah I hope he does more.It legit felt like something you would hear on college radio back in the day. Like, he's into cool edgy noise rock...hop I'm not doing him a diservice by saying that. It really reminded me of Sonic Youth or Pussy Galore but better.He's got good taste in music.
(DIR) Post #AQWEQLblTAA9buGUeu by ins0mniak@cyberstorm.one
2022-12-12T04:08:56.933731Z
3 likes, 0 repeats
@p @sjw @coyote @shitpisscum @hakui He even had a chat set up. I was sick, so I made sure to say hi, and then I just let it stream while I slept.Dude, he did a really good job.
(DIR) Post #AQWFjpBBqciQmSgbdA by coyote@pl.lain.sh
2022-12-12T04:23:55.058102Z
4 likes, 0 repeats
@ins0mniak @sjw @p @shitpisscum @hakui Thanks man
(DIR) Post #AQWFo35E5zcZ3puXi4 by coyote@pl.lain.sh
2022-12-12T04:25:13.228307Z
2 likes, 0 repeats
@ins0mniak @sjw @p @shitpisscum @hakui really glad you dropped by
(DIR) Post #AQWGM0YQ0Oj53wl4xU by MK2boogaloo@freespeechextremist.com
2022-12-12T04:31:25.572539Z
3 likes, 0 repeats
@ins0mniak @p @coyote @hakui @shitpisscum @sjw where can I see it?
(DIR) Post #AQWGfW3l5pA6HFig9w by ins0mniak@cyberstorm.one
2022-12-12T04:34:36.435124Z
2 likes, 0 repeats
@coyote @sjw @p @shitpisscum @hakui So, yeah,I mean I consider you a friend, but I think it's cool as fuck what you're up to.You put on a cool show and did it way better than any MTV-whatever corpo clown ever could. It's punk rock/hacker tier coolness.
(DIR) Post #AQWGpycDmHl7jmpLqC by ins0mniak@cyberstorm.one
2022-12-12T04:35:45.894198Z
2 likes, 0 repeats
@coyote @sjw @p @shitpisscum @hakui Yeah, it was a blast, sorry I couln't be more engaged. I just curled up in a ball and jammed out, haha.
(DIR) Post #AQWHQOguJ5Ah2CNydM by coyote@pl.lain.sh
2022-12-12T04:43:20.647154Z
5 likes, 0 repeats
@MK2boogaloo @sjw @ins0mniak @p @shitpisscum @hakui it's offline but here's a link and a screenshot https://radio.lain.sh/
(DIR) Post #AQWHWzkFSDrfh05v7o by coyote@pl.lain.sh
2022-12-12T04:44:33.064987Z
2 likes, 0 repeats
@ins0mniak @sjw @p @shitpisscum @hakui You too man, you're a friend. Thank you, I hope to entertain and stimulate. I'm glad you enjoyed it :) and no need for apologies, just glad you joined
(DIR) Post #AQWHciH7JsUtFSCAVM by PhenomX6@fedi.pawlicker.com
2022-12-12T04:45:35.887186Z
3 likes, 0 repeats
@p @sjw @coyote @shitpisscum yo @despair you might wanna see this
(DIR) Post #AQWIdF3LYI7yrSZPns by ins0mniak@cyberstorm.one
2022-12-12T04:56:37.120754Z
2 likes, 0 repeats
@coyote @sjw @p @shitpisscum @hakui Word bro, I'm really looking forward to you doing another castkicking back, rocking out on the net.
(DIR) Post #AQWJ2Dce0a9nfCzSjo by coyote@pl.lain.sh
2022-12-12T05:01:24.751868Z
2 likes, 0 repeats
@ins0mniak @sjw @p @shitpisscum @hakui I did two impromptu things since then, just did a jazz/down tempo/classic jazz 3h stream last night, I was posting about it, I'll cc you next time if I can
(DIR) Post #AQWJ46CSZjjPDsdhfU by coyote@pl.lain.sh
2022-12-12T05:01:45.439006Z
1 likes, 0 repeats
@ins0mniak @sjw @p @shitpisscum @hakui the next big one will be jan 7th
(DIR) Post #AQWJOv0NOQ9gaFumZM by ins0mniak@cyberstorm.one
2022-12-12T05:05:16.843436Z
2 likes, 0 repeats
@coyote @sjw @p @shitpisscum @hakui Hels yeah. just send me a date link or whatever so I can put it on my normie calander haha.Like dude, I'll get some drinks on and jam out.
(DIR) Post #AQWJWDUp2f4zxZdTmK by ins0mniak@cyberstorm.one
2022-12-12T05:05:49.403962Z
2 likes, 0 repeats
@coyote @sjw @p @shitpisscum @hakui I like jazz too.
(DIR) Post #AQWJYyMvk1N7ucG5ia by coyote@pl.lain.sh
2022-12-12T05:07:19.552105Z
1 likes, 0 repeats
@ins0mniak @sjw @p @shitpisscum @hakui I have been doing them off the cuff, dec 7th is ambient/drone night though, part I
(DIR) Post #AQWJbCcdibw2hIfaMa by coyote@pl.lain.sh
2022-12-12T05:07:44.283929Z
2 likes, 0 repeats
@ins0mniak @sjw @p @shitpisscum @hakui me too man, played some monk
(DIR) Post #AQWOmklpb0uTYwIQV6 by PhenomX6@fedi.pawlicker.com
2022-12-12T06:05:51.595783Z
0 likes, 0 repeats
@p @sjw @coyote @shitpisscum also @alex I know you mess with the pleroma codebase too for your fork what do you think of this?
(DIR) Post #AQWX0hEiKdggHyxuvA by p@freespeechextremist.com
2022-12-12T07:38:03.605145Z
8 likes, 1 repeats
@PhenomX6 @alex @coyote @shitpisscum @sjw Alex "Branding Guy" Gleason doesn't know shit about shit, he literally can't hack it. Time is expensive enough without dragging that particular idiot into the thread.
(DIR) Post #AQWX7mne2tTVZRgVoe by Soy_Magnus@detroitriotcity.com
2022-12-12T07:39:20.091537Z
1 likes, 0 repeats
@p @sjw @PhenomX6 @alex @coyote @shitpisscum :dancing_questionmark: what the shit howndare u¡ his advice on bathtub hrt is priceless
(DIR) Post #AQXTTKv6B3RSoc9SPg by p@freespeechextremist.com
2022-12-12T18:33:07.638789Z
2 likes, 1 repeats
@Soy_Magnus @PhenomX6 @alex @coyote @shitpisscum @sjw It's bat jizz and sticks, he eats bat jizz and sticks. It's loopy shit. I don't recommend.
(DIR) Post #AQXq9mjnL978FDViBk by despair@gearlandia.haus
2022-12-12T22:03:06.131606Z
1 likes, 1 repeats
@PhenomX6 i'm on the latest check-in, problems cleared up when i reset the federation queue sizes to the old values and added the indexes in https://git.pleroma.social/pleroma/pleroma/-/issues/2941#note_95273then cleaned up and made postgres do a query strat analysis afterward
(DIR) Post #AQXqafp59mqUcLnyMq by shitpisscum@social.mrhands.horse
2022-12-12T22:52:08.911213Z
1 likes, 0 repeats
@p @sjw @coyote >ridiculous long-running queryIdk what would be considered ridiculously long here but here's a recurring query that's running between 15 and 20 seconds (double quotes are probably from writing to a csv file), also there's always a few of them:SELECT a0.""id"", a0.""data"", a0.""local"", a0.""actor"", a0.""recipients"", a0.""inserted_at"", a0.""updated_at"" FROM ""activities"" AS a0 WHERE (coalesce((a0.""data"")->'object'->>'id', (a0.""data"")->>'object') = $1) AND ((a0.""data"")->>'type' = $2) AND (NOT (a0.""actor"" = ANY($3)))
(DIR) Post #AQXqg10BqBPBkeY18S by shitpisscum@social.mrhands.horse
2022-12-12T22:53:07.485223Z
4 likes, 0 repeats
@Cumsocks @sjw @p @coyote Aww man she's just like me 😍
(DIR) Post #AQXr9RIh8tzpiFEYDI by shitpisscum@social.mrhands.horse
2022-12-12T22:58:26.050310Z
2 likes, 0 repeats
@p @coyote @sjw Btw I set up a cron job to restart Pleroma every hour, should reduce the amount of remote activities it missses while I'm sleeping or away from home and unavailable to restart it so it has less shit to "catch up" if/when it's ever back to "normal"
(DIR) Post #AQXs4J9O7JdgwRzuEq by Cumsocks@freecumextremist.com
2022-12-12T23:08:43.112696Z
2 likes, 0 repeats
@shitpisscum @sjw @p @coyote :akko_fingerguns:
(DIR) Post #AQYPilzxZr8kTzUTqq by p@freespeechextremist.com
2022-12-13T05:25:48.503321Z
3 likes, 0 repeats
@shitpisscum @coyote @sjw Yeah, that's a timeline fetch."Ridiculously long" is anything more than a few seconds.
(DIR) Post #AQYPp2q9s9R8SEte52 by p@freespeechextremist.com
2022-12-13T05:26:56.510727Z
2 likes, 0 repeats
@shitpisscum @coyote @sjw I believe this to be a bad idea.You could kill it if the rate of 5xx errors goes too high and run it in a loop to make sure it restarts; I used to do that with FSE.
(DIR) Post #AQZXQbLhQUVt27StRA by shitpisscum@social.mrhands.horse
2022-12-13T18:26:51.567643Z
1 likes, 0 repeats
@p @sjw @coyote Yea it's not really a "solution" it's more like "keeping it on life support untill I unfuck Postgres"