Conversation

Notices

1. チャノさん :verified: (japananon@pl.anon-kenkai.com)'s status on Tuesday, 03-Jan-2023 00:12:01 JST チャノさん :verified:
   ..oof, I think the DB here is just about ready to give up the ghost. I'm getting 500 errors all over the place
   • sev (7@collapsitarian.io)'s status on Tuesday, 03-Jan-2023 00:14:00 JST sev

     in reply to
     @JapanAnon That seems to be common right now, following the 2.5 release of Pleroma. I wish I had some good advice, but I had to rebuild collapsio for similar reasons. Good luck!
   • チャノさん :verified: (japananon@pl.anon-kenkai.com)'s status on Tuesday, 03-Jan-2023 00:14:00 JST チャノさん :verified:

     in reply to

     • sev
     @7 Guess I've delayed the inevitable long enough. Time to set up a new instance of something.
   • 寮 (ryo@social.076.moe)'s status on Tuesday, 03-Jan-2023 00:27:57 JST 寮

     in reply to
     So you're experiencing a social.076.ne.jp now.
     Really sucks how Pleroma has a hard dependency on Postgres, which is really the root of the problem.
   • チャノさん :verified: (japananon@pl.anon-kenkai.com)'s status on Tuesday, 03-Jan-2023 00:46:31 JST チャノさん :verified:

     in reply to

     • 寮
     @ryo It has finally happened, yes.
     
     I can still receive and send new messages, at least...
   • 寮 (ryo@social.076.moe)'s status on Tuesday, 03-Jan-2023 00:59:05 JST 寮

     in reply to
     Spoiler alert: it will start getting worse and worse until it gets to the point the instance becomes entirely unusable.
     We experienced this here not so long ago, so I know what will happen next.