• 1984@lemmy.today
    link
    fedilink
    English
    arrow-up
    15
    ·
    9 months ago

    I would comment on this but since federation is broken…this won’t be seen until the instance admin restarts Lemmy and federation works once again.

    • BlueÆther@no.lastname.nz
      link
      fedilink
      English
      arrow-up
      12
      arrow-down
      1
      ·
      edit-2
      9 months ago

      Federation seems to be working fine from where I stand?

      Edit:

      Edit 2:

      Even the edit federated out to your instance fine…

      • 1984@lemmy.today
        link
        fedilink
        English
        arrow-up
        6
        ·
        9 months ago

        I think it works for a while after restart of the server, and then stops working. Yesterday I was making comments that didn’t federate until 12 hours later when I assume the instance admin restarted the server.

        • BlueÆther@no.lastname.nz
          link
          fedilink
          English
          arrow-up
          5
          arrow-down
          2
          ·
          9 months ago

          My instance has been uo for over 3 days since 0.19.1 update with no issues - very little load though

          • 1984@lemmy.today
            link
            fedilink
            English
            arrow-up
            3
            ·
            9 months ago

            Yeah it seems to work for some instances with 0.19.1 but Lemmy.today has issues and feddit.de as well, just from what I’ve heard. Probably plenty more.

      • Skull giver@popplesburger.hilciferous.nl
        link
        fedilink
        English
        arrow-up
        5
        ·
        edit-2
        9 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!