Conversation

Notices

1.  (mint@ryona.agency)'s status on Sunday, 01-Sep-2024 06:31:05 JST 

   • 
   • feld
   • Tij
   • nukie
   • Phantasm
   @phnt @Tij @feld @nukie Oh, it crashed in entirety, but got restarted by healthcheck script. Nothing in logs except hundreds of DBConnection.ConnectionErrors, but there's also a bunch of "ERROR 57014 (query_canceled)" and "unknown registry: Pleroma.Web.StreamerRegistry". Either way, with restarts once in a while it's slowly chipping through the queue, about 70k jobs done.
   • feld (feld@bikeshed.party)'s status on Sunday, 01-Sep-2024 06:32:47 JST feld

     in reply to

     • Tij
     • nukie
     • Phantasm
     @phnt @nukie @Tij @mint if we can figure out what gets caught in the fast crash loop we can change the way it starts that service to prevent that from crippling the app
   • Phantasm (phnt@fluffytail.org)'s status on Sunday, 01-Sep-2024 06:32:51 JST Phantasm

     in reply to

     • feld
     • Tij
     • nukie

     @mint @feld @nukie @Tij Yeah that's the issue I usually run into.

     I have no idea how the supervisor tree in Pleroma looks like, but my theory is that after enough db_connection errors, the error slowly goes up and eventually reaches Pleroma's own supervisor. The maximum number of restarts is set to 3 in the default config and after that is exceeded, it exits and init restarts it.

     There's a somewhat rare case when the Pleroma application completely shuts down, but the system process itself still exists and therefore it doesn't get restarted by init. That's the issue I talked about.