Hi all. Several of you have reported problems with fedia.io not federating with other instances correctly.

The cause is that rabbitmq crashed, but not all the way. It crashed to the point where new connections would timeout, but the service was still running such that it wouldn’t auto restart. I will be creating some automation to detect that proactively and restart rabbitmq if/when it happens again.

  • jerry@fedia.ioOPM
    2·
    2 days ago

    ok - the queues are processing again. I will work on a more permanent fix after dinner

    • Chozo@fedia.io
      2·
      23 hours ago

      Sorry to nag, but it looks like it might be acting up again lol. Doesn’t look like any sync has happened for 5 hours.

        • magnetosphere@fedia.io
          2·
          23 hours ago

          Thank you for all your hard work. I am experiencing the same problem, and was just browsing Fedia Discussions to see if anyone else had reported it. Again, thanks!

          • jerry@fedia.ioOPM
            3·
            22 hours ago

            It’s almost caught up. My apologies. I am trying to get it fixed permanently.

            • Chozo@fedia.io
              2·
              22 hours ago

              It’s appreciated! <3

              While you’re working on a more permanent fix, is there a preferred way we should let you know about hiccups like this? Or is pinging you in a thread in this magazine sufficient?

              • jerry@fedia.ioOPM
                3·
                22 hours ago

                Note that even once I get this fixed, there will inevitably be another problem crop up. Posting here is fine, but an email to jerry@infosec.exchange or a ping to @jerry@infosec.exchange (my mastodon account) would probably be faster (note, when federation breaks here, messages to @jerry@infosec.exchange wouldn’t get through from fedia.io…