thank you again for your help! I was at the end of my rope and you gave me the idea that solved it
be aware that this is fixed now
be aware that this is fixed now
be aware that this is fixed now
Thanks. It’s a strange problem that only happens when trying to post directly to a community/magazine that resides on another instance. So this works fine because this community it hosted locally. I think I understand when but hoping to get some clarification.
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…
It’s almost caught up. My apologies. I am trying to get it fixed permanently.
:( I’m working on it
ok - the queues are processing again. I will work on a more permanent fix after dinner
ok - rabbitmq started having prroblems with the delivery queue again. I got it going again. Those messages should be delivered soon.
I am not 100% sure. Fedia.io is running on a beast of a server, and so long as it’s working correctly, it should be able to deliver it instantly. But that doesn’t mean that the receiving servers are able to consume and render them that fast.
Once it is more reliable, then I’ll agree, but thank you
there isn’t an inteval per se - I don’t yet know why it’s not immediate. It’s possible that the delay is on the receiving side - the server that fedia.io is quite substantial and unless there is some sort of bug, the processing should happen immediately.
Outbound federation was indeed broken. I fixed it, but there was a huge backlog the server had to work through, which took about 12 hours to complete. I just checked and everything appears to be working ok. I am going to create some automation that will detect and alert on this (or other issues) happening in the future.
Not entirely. It looks like the rabbit issue was only impacting one of the queues (“deliver”), though I would have expected that to impact things like microblog too. All I can say with clarity is that the instance was operating in a very unhealthy state.
The queue appears like it’ll take several hours to flush, but it’s working.
I found the problem and the queues are running now. I will make a thread about it.
Thank you for the problem report. I will be looking into this later today.
I’ve been in the business for about 25 years. I have a hard time recommending people jump in at this point, or at least to understand the market now. While there is constant talk of “unfilled cyber jobs”, the reality is that many people with experience are struggling to find a job in the field.
If you can get in and find a stable spot at a good company, it’s a great career, but those are getting hard to find I fear. Anyhow, please do a bit of reading about the job market for cyber security before making a decision.