silly judgemental post not meant to be taken too seriously (unless you agree with me in which case im dead serious)

  • jivandabeastA
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    10 months ago

    lock up my entire server until i reboot

    Check the ram usage on postgres. Theres a memory leak issue thats being monitored with a proposed fix in the next version (which is upgrading to the newer version of postgres)

    • Toribor@corndog.social
      link
      fedilink
      English
      arrow-up
      2
      ·
      10 months ago

      Thank you! I was secretly hoping someone might have a quick suggestion of something to try. I’ll see what I can find out.

      • jivandabeastA
        link
        fedilink
        arrow-up
        2
        ·
        10 months ago

        Yeah no problem! My workaround solution is simply just restarting the postgres container when i notice ram usage spiking

        • Toribor@corndog.social
          link
          fedilink
          English
          arrow-up
          1
          ·
          10 months ago

          Usually by the time I notice the server is already unreachable over SSH but I’ve been considering adding manual healthchecks to my containers. Paired with the docker-autoheal project it’s been a really low effort way for me to keep services healthy without a lot of babysitting. I’m more nervous about implimenting it for something like a stateful database though, but I suppose it’s no different than manually issuing a docker restart command.