Hi,

Several posts I’ve made to /c/fountainpens have not made it to lemmy.world from the lemmy.sdf.org instance.

If you compare these two urls, you can see that the top post (and several others) are only visible when viewed from sdf:

https://lemmy.world/c/fountainpens https://lemmy.sdf.org/c/fountainpens@lemmy.world

I’ve looked at the debugging tool and the sdf instance thinks that outbound lemmy.world is up to date, so has lemmy.world rejected the posts somehow?

It seems to happen non-deterministically. Some posts have made it through. This has been ongoing for at least a couple of weeks now.

Any ideas?

Edit: this post did federate… could it be to do with posts with images or something?

  • Rooki@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    2 months ago

    Hi,

    we will investigate this matter, we have some issue on slrpnk.net too and i think it has some relation to yours.

    Thanks for your patience.

    • vext01@lemmy.sdf.orgOP
      link
      fedilink
      arrow-up
      0
      ·
      2 months ago

      Thanks for getting back to me! I hope it can be fixed because it’s a community I mod.

      Out of interest, how do you debug such things? Is there a log file you inspect? Is it public?

      • Rooki@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        2 months ago

        Logfiles and partially a public site i forgot what url directly but it tells you the desync / delay of certain federations between instances.

  • MrKaplan@lemmy.worldM
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 months ago

    It does indeed seem to have been an issue with loading metadata for the image at the time.

    I’m not sure if sdf pict-rs was slow at the time or what was causing it at this point, but Lemmy cut it off after 9 seconds of processing the post and that’s where it failed. Unfortunately the logs don’t give a reason currently.

    If you remove your vote on the post and restore it after a minute it will likely trigger it to get processed properly, although this is obviously not a usable solution.

    We’ll have to look into if we can improve this somehow.