Conversation

Notices

1. Embed this notice
   寮 (ryo@social.076.moe)'s status on Thursday, 22-Dec-2022 22:17:01 JST 寮

   • チャノさん
   Seems like @JapanAnon 's instance is starting to show first signs of breakage similar to what 076 SNS did back on Pleroma before it got completely borked.
   Perhaps something's inherently wrong with Pleroma itself now?
   • Embed this notice
     寮 (ryo@social.076.moe)'s status on Thursday, 22-Dec-2022 22:54:37 JST 寮

     in reply to

     • チャノさん
     Basically, I loaded your account on your instance, and manually had to click 古いステータス before any of your posts would load.
     Then as I was scrolling down, error 500 appeared in a red banner a few times.
     
     Although seems to be fine again now.
   • Embed this notice
     チャノさん (japananon@pl.anon-kenkai.com)'s status on Thursday, 22-Dec-2022 22:54:38 JST チャノさん

     in reply to
     @ryo What's happening now?
   • Embed this notice
     寮 (ryo@social.076.moe)'s status on Thursday, 22-Dec-2022 23:56:45 JST 寮

     in reply to

     • チャノさん
     Whatever your choice will be, do it sooner rather than later.
     Loli frog reacted too late, and no amount of vacuuming the DB, restarting the entire server, and so on could fix it.
     It made me hate Postgres even more than I already did from my experience having to fix web apps that were using it.
     Good old MySQL/MariaDB is so much better!
   • Embed this notice
     チャノさん (japananon@pl.anon-kenkai.com)'s status on Thursday, 22-Dec-2022 23:56:48 JST チャノさん

     in reply to
     @ryo Yeah, I get problems from time to time. Database just chugs periodically.
     
     I wanted to do a vacuum job on it, but my free disk space is too small. I need to either port the instance to a new server or spin up something new, and I haven't decided what to do yet. But moving the existing instance looks like it'd be a big pain in the ass, and it probably wouldn't fix the database troubles.