Lemmy is now upgraded to 0.18.5! This is a much needed bug fix that fixes federation of admin actions.

Unfortunately the server crashed when shutting down nginx (wtf), so there was about 5 minutes of downtime as I hopped onto the console to power cycle it. This is the second time that’s happened now, so further investigations will be had =)

  • Shadow@lemmy.caOPM
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 year ago

    Was actually a whole kernel panic, it looks like all IO on the box completely hung when the nginx docker container was stopped. Kinda a mystery, wondering if it’s a kernel bug.

    • MrGG@lemmy.ca
      link
      fedilink
      English
      arrow-up
      7
      ·
      1 year ago

      Oh damn! What kind of memory usage and open file handles does nginx typically use for this instance?

      • Shadow@lemmy.caOPM
        link
        fedilink
        English
        arrow-up
        11
        ·
        1 year ago

        Our usage is really low across the board. I’ve thrown as much ram at postgres as its willing to use, and right now after a clean boot we’re only using 4gb of ram.

        Other than some poor sql, lemmy is actually really performant. There’s a lot more attention on the db now though which has helped a lot.

        I’ll try to do a post this weekend with some data graphs.

        • Anony Moose@lemmy.ca
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          That would be awesome! I’m glad to hear that Lemmy is performing in general and that the SQL woes are being addressed