I just noticed that my active and hot are 3 days old, it looks like this server is being hit with this bug where the hot calculator dies. Currently, there are fixes in the works and it may be worth cherry picking them or restarting the server during a down time until the fixes make it into the next release.
Unfortunately, we’re stuck with the bug until we upgrade to a version without it. Restarting has been suggested, but the problem with that is that the outbound queue is held in RAM, so it gets lost with a restart.
We’ll upgrade our version as soon as humanly possible
Yep :/ for any readers here is the issue in github.
Thanks for the update. The outbound queue is held in RAM … what could possibly go wrong? 😂
I have set a cronjob on my instance to restart Lemmy via docker_compose every 4 hours. It cause a small 30s downtime every 4 hours, but should be preferable to having the timelines stale.
Looks like there’s a new release coming soon that hopefully contains a fix for this.
Yeah I’ve been wondering about that. Hope this gets fixed soon!
