Due to this bug that results in the Hot listing not updating, I’ve scheduled lemmy to automatically restart every hour on the hour.

When this occurs you may receive 502 errors briefly.

  • Lodion 🇦🇺OPMA
    5·
    2 years ago

    Ok, this is now scheduled to occur hourly, on the hour. Will cause a few seconds of 502s while lemmy is restarted.

    • hikarulsi
      2·
      2 years ago

      what is the instance running on at the moment? perhaps it might be helpful to have some load balancing fronting the instance

      • Lodion 🇦🇺OPMA
        3·
        2 years ago

        Details on the server stuff is over here.
        This issue isn’t load related, simply a bug. Load balancing wouldn’t help in this case.

        • hikarulsi
          2·
          2 years ago

          thank you for the information

          let us know the error/warning message, let’s see if anyone happen to have the knowledge. Remember to redact some key info

          • Lodion 🇦🇺OPMA
            2·
            2 years ago

            If you get the error, it will literally be “502 error” on a plain white page. Chances are unless you’ve just clicked a link or hit reply/submit, you’ll never see it.

            • hikarulsi
              2·
              2 years ago

              The likely reason would be server overload, haven’t look into the lemmy stack. Perhaps monitor cpu, ram and cache usage (if any) to see if there is any correlations to the 502s

              • Lodion 🇦🇺OPMA
                2·
                2 years ago

                No… 502 is due to me restarting the lemmy process, due to the known bug I linked.

                • hikarulsi
                  2·
                  2 years ago

                  understood, i guess it is up to the dev or pull request to fix it for now