Notices by ??? ???? ?????? :verified: (ryan@ryanthomas.org)

Would these modifications of the Rebased logo be a problem if I weren’t a single-user instance?

Anything of note here? Only two output rows from that sql command:

I took a nap so left it alone for a while, bumped remote_post_retention_days down to 28 (not that it matters here, I had meant to do that anyway), restarted pleroma, then ./bin/pleroma_ctl database vacuum analyze and rebooted when done. So far, memory is still higher than I remember it being in the past, which you’ve already explained, but swap is lower, and things that weren’t loading are loading fine, and I haven’t seen any more gateway timeout errors.

If I get issues again, could it be helpful to purge old remote content and do a vacuum full? Is it a good idea to do that periodically anyway? And should I stop my pleroma service while doing so or just expect it may cause a few hours downtime?

Appreciate your help and anyone reading this who might be inspired to chime in! Best

Thanks for following up

I’m probably missing something obvious here?

Also, I found a binary /opt/pleroma/lib/ecto_psql_extras-0.7.4/ebin/Elixir.EctoPSQLExtras.LongRunningQueries.beam but not sure what to do with it.

Database is unfortunately grinding to a halt. It’s been inconsistently responsive since I migrated, mostly smooth, but today I’m getting gateway errors and slow ssh; rebooting seems to help for a few minutes.

Memory usage looks higher than usual

You might also recall I had an issue with web push notifications on pleroma with soapbox-fe, for whatever reason. They are working now

Just installed and migrated to rebased with soapbox on Ubuntu 20.04.5 LTS.

Didn’t bother backing up directories but did back up the db via:

I otherwise followed @alex ‘s instructions linked below verbatim except that my mv command doesn’t seem to let me overwrite/merge folders even with -f and trailing /* on the source, so I used cp -r instead. Furthermore, instead of stopping and starting pleroma from /opt/pleroma/bin/pleroma_ctl stop/start as the pleroma user, I had to use sudo systemctl stop/start pleroma.

Also, that the requisite version of postgresql is installed can be confirmed via apt show postgresql

https://gitlab.com/-/snippets/2411739

RT: https://ryanthomas.org/objects/5e3104c6-a3d0-43f5-bd9a-335e00de474d

@GoodPerson I could be way off but I get the impression the Soapbox devs aren’t prioritizing the Pleroma backend anymore. I’ve bounced back and forth and landed on PleromaFE

@GoodPerson Funny I thought Gleace was an SJW with a sense of humor. I completely missed this saga.

I self-host native Pleroma and wondered if I should migrate to Rebased too but haven’t heard any reason to yet

@alex Eh, it’s not like HDMI is deprecated, they can just plug in an external “smart” device like a TiVo or whatever the kids are overpaying for these days