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.
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.
Ok, this is now scheduled to occur hourly, on the hour. Will cause a few seconds of 502s while lemmy is restarted.
what is the instance running on at the moment? perhaps it might be helpful to have some load balancing fronting the instance
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.
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
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.
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
No… 502 is due to me restarting the lemmy process, due to the known bug I linked.
understood, i guess it is up to the dev or pull request to fix it for now