So far, we are the only ones having the problem. It is almost certainly because we have many more accounts/activity than others. The current problem may be a rabbitmq bug

it was indeed broken again. should be fixed now

The modlog function in lemmy/mbin can be a bit confusing. I don’t think the moderation actions of one instance propagate to the modlog of another instance. I think that is only really problematic in cases where the moderation action was taken on the home instance of a magazine/community.

thanks. I think the name of the instance is the most important part - I can test of federation with them to see what went wrong.

At the moment, there isn’t anything going on that would cause that. Can you tell me which other instance/which thread so i can try to troubleshoot?

I am investigating…

Did it take a long time before that error came back?

In the worst case scenario, fedia.io will be around for at least 5 more years (that is apparently the standard subset timeline). I have many more domain names if the worst comes, but there is a lot of expectation that the .io may somehow be saved due to the incredible amount of infrastructure built around it (GitHub.io, dockerhub.io, and of course fedia.io among many others)

I see it - it’s working again and I’m trying to figure out why rabbitmq died yet again.

I don’t know yet - it’s definitely not expected, so my guess is an unintentional bug in mbin somewhere. I am hoping to find a way run a profiler or something similar to see what it’s doing.

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.

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