Notices by shitpisscum (shitpisscum@social.mrhands.horse)

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Thursday, 09-Mar-2023 05:26:35 JST

in reply to

@coolboymew @roboneko @shitpisscum UPDATE it works in Husky it's just PleromaFE that can't recognize it as an image lol

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Thursday, 09-Mar-2023 03:47:19 JST

@meso @Crusader @captain_arepa @marine @Bloomfer @eris @n3f_X @peemasons @bot @shitpisscum @Hoss @creamqueen @pomstan No, seriously, who's that?

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Tuesday, 07-Mar-2023 01:51:38 JST

shitpisscum

in reply to

@meso @lina @splitshockvirus lmao what did I miss?

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Saturday, 11-Feb-2023 21:55:08 JST

shitpisscum

in reply to

@pisscumshit @shitpisscum Yea looks like it. The first restored db was definitely broken, did another backup with --quote-all-identifiers also I copied the .pgdump file to a new machine instead of running it directly from the old machine.

>Looks like you're still on 2.4.3
Right now yea but I'm definitely upgrading to 2.5.0 or whatever the latest version is

>500s throws every second
It's effectively been down for over a month, give it some time

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Saturday, 11-Feb-2023 05:13:08 JST

shitpisscum

cool_boy_mew

@coolboymew Can't find the screenshot but there's also one saying something like "y'all ever dring protein shakes and imagine it's futa forcing you to drink her cum?" lol

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Saturday, 11-Feb-2023 04:56:57 JST

shitpisscum

cool_boy_mew

@coolboymew I'd buy that

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Saturday, 11-Feb-2023 03:59:43 JST

shitpisscum

in reply to

@p @sjw @1ns0mniak @cope @miklol2 @graf @mint Planned to do the update tonight but I'm kind of busy, will probably do it tomorrow or wednesday (why wednesday in particular , well I'll leave it up to you to figure out), but decided to do a quick experiment last night: made another backup of the original db with --quote-all-identifiers and tried restoring it (didn't srop anything, a separate db, literally called it pleroma1 lol). Anyway, it's been stuck on creating INDEX "public.activities_visibility_index" for almost a full day now. Also had the same issue when restoring the current db (the one pleroma's using rn), it also took more than 24 hours to build that index. My question is, is this normal for pleroma's db or does that mean the original db itself is fucked and I'm just restoring a broken backup?

inb4 I told you not to do it in all caps: I didn't drop anything this is a separate db, the old one is still "running"

inb4 update: I will and you will be notified, I'm just asking whether this particular behavior is normal or indicates some additional issues

in4 doxxed you because you're gonna update pleroma on wednesday: :pleromatanshrug:

inb4 are you drunk: not yet

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Friday, 10-Feb-2023 06:53:18 JST

shitpisscum

@sjw @1ns0mniak @cope @p @miklol2 @graf serious question, what's the deal with the source install? I mean there has to be at least some real world advantage other than being able to tell people you built some software from source lol

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Friday, 10-Feb-2023 06:51:47 JST

shitpisscum

@graf @sjw @1ns0mniak @p @miklol2 yea, from 12 to 14

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Friday, 10-Feb-2023 06:51:38 JST

shitpisscum

@p @sjw @1ns0mniak @cope @miklol2 @graf Going to sleep soon, a quick recap: Seems to be running slightly better after VACUUM ANALYZE but nothing dramatic, still keep in mind it's effectively been offline for the past 3 days. Gonna leave it running over night, if it's still running tomorrow I'll try updating pleroma.

One question, is a copy of config.exs enough to restore pleroma (OTP) in case of a failed upgrade? Also what's the worst that could happen if I attempt the upgrade but it turns out it was the database that was broken (not properly restored or whatever)?

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Friday, 10-Feb-2023 06:51:03 JST

shitpisscum

in reply to

@sjw @p @miklol2 @graf
> just let it run for a little bit
It's been running like this for 3 days already, CPU on the db server constantly at 100% so I don't really think it's going to fix itself any time soon lol

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Friday, 10-Feb-2023 06:51:01 JST

shitpisscum

in reply to

@1ns0mniak @sjw @p @miklol2 @graf Ok but here's the weird part: I migrated the db to a more powerful dedicated server and now it's running much WORSE than it was

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Friday, 10-Feb-2023 06:50:56 JST

shitpisscum

@cope @sjw @1ns0mniak @p @miklol2 @graf Already nuked oban jobs. You're telling me it can actually be restored from 12 to 14 if I dump it as .sql instead of pleroma's .pgdump?

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Friday, 10-Feb-2023 06:50:53 JST

shitpisscum

@cope @sjw @1ns0mniak @p @miklol2 @graf I mean it restored but is running like absolute shit, way worse than it did on that free tier VPS

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Friday, 10-Feb-2023 06:50:51 JST

shitpisscum

@sjw @1ns0mniak @cope @p @miklol2 @graf Nope didn't do that, should I?

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Thursday, 09-Feb-2023 02:51:21 JST

shitpisscum

in reply to

@mint @sjw @p @miklol2 @graf one question, how do I make sure it doesn't do that "error deleting write protected folder" thing that completely bricks everything and requires a manuall reinstalling?

shitpisscum (shitpisscum@social.mrhands.horse)'s status on Thursday, 09-Feb-2023 02:44:44 JST

shitpisscum

in reply to