Fediverse

28422 readers

891 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Posts must be on topic.
Be respectful of others.
Cite the sources used for graphs and other statistics.
Follow the general Lemmy.world rules.

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 1 year ago

MODERATORS

ruud@lemmy.world

TragicNotCute@lemmy.world

Xylinna@lemmy.world

MrCenny@lemmy.world

automodbeta@lemmy.world

woelkchen@lemmy.world

294

PSA: the federation problem is still present in Lemmy 0.19.1, the GitHub issue has been reopened (github.com)

submitted 11 months ago* (last edited 11 months ago) by Blaze@sh.itjust.works to c/fediverse@lemmy.world

60 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] skullgiver@popplesburger.hilciferous.nl 5 points 11 months ago* (last edited 11 months ago)

I have mh suspicions that this is some kind of deadlock issue. After fucking up my config during am upgrade (too many database connections, too many workers) the new multithreaded federation thingy seemed to become quite unstable. From what I could tell, the threads that are supposed to deal with federation all broke/shut down, but didn't get automatically restarted again, leaving some messages and instances in limbo until the entire server got restarted.

After fixing my database connection issue and reducing the amount of workers, I don't think I've encountered many issues since. I occasionally click the little icon above a post to check if my response had reached the community server, and usually it does, pretty quickly.

This issue sounds awful to have to debug, best of luck to the Lemmy devs in finding a fix!