When I look at https://fedia.io/all/newest right now there seems to be very little getting through today, with only 3 new threads in the past 10 hours.

Edit: 4 now that I’ve posted this one, and now I notice that they’re all from local users.

  • jerry@fedia.ioM
    3·
    10 months ago

    Hi all. I am working on it. I am trying to figure out what the problem is this time rather than just restarting the containers.

      • e-five@fedia.io
        1·
        10 months ago

        It’s also possible there are no local subscribers, or weren’t until now. It’s one of the things we need to fix after updating subscriber counts to show accurate information rather than just local information, as it’s unclear if a magazine has no local subscribers anymore

          • e-five@fedia.io
            1·
            10 months ago

            Hmm… looking at their instance list and stuff, I get the feeling they might consider fedia an “inactive” instance (based on the information being out of date), which is a bug lemmy has where after upgrades it marks instances as inactive and never updates it again. I will try to get in contact with their admins to confirm

            Edit: quick edit, speaking with another german instance owner they said they have the same problem with feddit.de right now and have already spoken to the admins and already taken steps to reset active state but it isn’t happening, perhaps more debugging is needed or maybe this is the lemmy federation issue people have been discussing

            Edit edit: they say they’re waiting for https://github.com/LemmyNet/lemmy/issues/4288#issuecomment-1879052639 to be merged which looks hopefully soon

    • e-five@fedia.io
      0·
      10 months ago

      if there’s anything people can help with don’t hesitate to ask in matrix!

      One thing I wanted to raise to your attention was asdfzdfj’s change to persist logging for docker setups which might make it easier to debug if your logs aren’t persisted between container restarts

      I mentioned in matrix but just in case since it’s a bit of a gotcha for people that run in docker:

      as a headsup for anyone running docker, there was a recent change to persist storage of logging just merged. it requires creating a directory and changing permissions on it. the admin guide was updated here but you may need to mkdir -p storage/logs and sudo chown $USER:$USER storage/logs where you run docker from by next sync/release

      this may or may not be relevant to you depending on if sync’ing would change your compose setup

      • jerry@fedia.ioM
        2·
        10 months ago

        I am going to apply this upgrade this weekend. I spent a few hours looking through logs this morning but didn’t see anything obvious (there are a breathtaking amount of logs) so gave up and restarted the containers. Will look again when it fails after I make log storage persistent