Conversation

Notices

1. Embed this notice
   keithzg (keithzg@fediverse.keithzg.ca)'s status on Saturday, 04-Feb-2023 22:21:21 JST keithzg

   in reply to

   • lainy
   • feld
   @feld @lain OTP release, Ubuntu 22.04 server running on a DigitalOcean droplet with 1GB of RAM. It's especially baffling to me that I continue to get 502 errors even after I restart both the Pleroma service and nginx!
   • Embed this notice
     feld (feld@bikeshed.party)'s status on Saturday, 04-Feb-2023 22:21:22 JST feld

     in reply to

     • lainy
     Cc @lain this is crazy, can you share more details on your setup? OS, how it's deployed, specs?
   • Embed this notice
     keithzg (keithzg@fediverse.keithzg.ca)'s status on Saturday, 04-Feb-2023 22:21:28 JST keithzg
     I haven't had the time or effort to figure out why my #Pleroma instance keeps dying entirely periodically, or why no services being restarted can resurrect it, only rebooting the entire server works. But I've now "solved" the problem . . . I have an hourly cron job that reboots the server if it gets a 502 status. This is a truly insane solution that would not be acceptable if anyone else was using my site, but I find this acceptable personally ;)
     
     If anyone has any ideas on how to fix this in a more *proper* manner, I'm all ears . . .
     clacke likes this.