I’m still seeing cases where comments don’t seem to be federating correctly. For example:

Other instance aussie.zone
https://lemmy.world/comment/6786498 https://aussie.zone/comment/5886332
https://feddit.uk/post/6819925 https://aussie.zone/post/6020867
https://lemmy.ml/comment/7476880 https://aussie.zone/comment/5881947
https://lemmy.blahaj.zone/comment/5759107 https://aussie.zone/comment/5888459
https://midwest.social/comment/6313276 https://aussie.zone/comment/5889962

I’m not sure what the cause is, but the last few days it seems more of my comments are failing to federate than are succeeding.

    • Lodion 🇦🇺M
      link
      fedilink
      710 months ago

      Ok, for some reason practically all instances were flagged as “dead” in the database. I’ve manually set them all to be requeued… server is now smashed as it attempts to updated the ~4000 instances I’ve told it are no longer dead. See how this goes…

  • @[email protected]
    link
    fedilink
    6
    edit-2
    10 months ago

    I’m claiming federation issues as the reason my posts aren’t getting thousands of upvotes.

      • @[email protected]
        link
        fedilink
        3
        edit-2
        10 months ago

        Careful, or I’ll turn to the dark side and federation will become a dictatorship so fast it’ll make Palpatine spin in his grave. Darth No1orious 🤣

  • Lodion 🇦🇺M
    link
    fedilink
    510 months ago

    Ok, something is busted with the lemmy API endpoint that shows current federation state. It is currently showing nearly all remote instances as dead:

    But “dead” instances are still successfully receiving content from AZ, and sending back to us.

    • Lodion 🇦🇺M
      link
      fedilink
      510 months ago

      Ok, there’s more to this than I first thought. It seems there is a back end task set to run at a set time every day, if the instance is restarting at that time the task doesn’t run… this task updates the instances table to show remote instances as “seen” by AZ. With the memory leaks in 0.19.1, the instance has been restarting when this task is running… leading to this situation.

      I’ve updated the server restart cronjob to not run around the time this task runs… and I’ve again manually updated the DB to flag all known instances as alive rather than dead.

      Will keep an eye on it some more…

      For anyone curious, two of the bugs that are related to this:
      https://github.com/LemmyNet/lemmy/issues/4288
      https://github.com/LemmyNet/lemmy/issues/4039

  • @[email protected]
    link
    fedilink
    English
    4
    edit-2
    10 months ago

    I found that this post’s body text is best viewed on desk/laptop for anyone trying to make heads or tails of all the links on mobile. Edit: Looks like my idea that this issue was due to some instances not being on 0.19.2 has been shot out of the water.