Basically, the lemmy backend service for some reason marked every instance we federated with as inactive, which caused it to stop outbound federation with basically everyone. I have a few working theories on why, but not fully sure yet.
TL;DR lemmy bug, required manual database intervention to fix
This was a stressful start to a vacation!
For a more detailed working theory…
I’ve been doing a lot of infrastructure upgrades lately. Lemdro.id runs on a ton of containerized services that scale horizontally for each part of the stack globally and according to load. It’s pretty cool. But my theory is that since the backend schedules inactive checking for 24 hours from when it starts that it simply was being restarted (upgraded) before it had a chance to check activity until it was too late.
theory:
scheduled task checks instances every 24 hours
I updated (restarted it) more than every 24 hours
it never had a chance to run the check
???
failure
This isn’t really a great design for inactivity checking and I’ll be submitting a pull request to fix it.
@utzer It currently does, afaik. That's why I turned this off long ago, even though I found the feature quite useful. I might use it again in the future though if there will be credible signs this will no longer be the case.
For now, there are plenty of self-tracking apps if you're into this. I personally use Transistor when I am going on hikes or various trips. It's great if you want to have a journal of places with gpx tracks.
android
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.