Fedia.io federation woes
Hi all. Several of you have reported problems with fedia.io not federating with other instances correctly.
The cause is that rabbitmq crashed, but not all the way. It crashed to the point where new connections would timeout, but the service was still running such that it wouldn't auto restart. I will be creating some automation to detect that proactively and restart rabbitmq if/when it happens again.
Thank you! A thread I just posted made it to Lemmy instances within 15 minutes. The thread that didn't federate two days ago has found its way there too. Jerry is the best instance admin and Fedia.io is worth paying money for.
Once it is more reliable, then I’ll agree, but thank you
Are we still having trouble? A thread I posted 45 minutes ago hasn't shown up on the instance I posted it to yet. The "Open original URL" menu on the post goes to the Fedia page instead of LemmyWorld. It seems like a comment I posted 2 hours ago is also not appearing on the original instance, either.
ok - rabbitmq started having prroblems with the delivery queue again. I got it going again. Those messages should be delivered soon.
Seems to be busted again already.
ok - the queues are processing again. I will work on a more permanent fix after dinner
Sorry to nag, but it looks like it might be acting up again lol. Doesn't look like any sync has happened for 5 hours.
:( I'm working on it
Thank you for all your hard work. I am experiencing the same problem, and was just browsing Fedia Discussions to see if anyone else had reported it. Again, thanks!
It’s almost caught up. My apologies. I am trying to get it fixed permanently.
Cool, thanks for the prompt work.
be aware that this is fixed now
Working on it
I will check.
any guess why visibility on lemmy has been heavily affected, whereas from microfedi things looked normal?
Not entirely. It looks like the rabbit issue was only impacting one of the queues (“deliver”), though I would have expected that to impact things like microblog too. All I can say with clarity is that the instance was operating in a very unhealthy state.
The queue appears like it’ll take several hours to flush, but it’s working.
i salute you!
be aware that this is fixed now