The cause is unclear to me, but the processes that manage incoming and outgoing federation were "stuck" until I manually intervened. It's running now. I'm adding to my to-do list for after my job ends in 10 days to implement some sort of detection and hopefully automated restart for when this happens again.
this post was submitted on 20 Jun 2024
14 points (100.0% liked)
Fedia Discussions
31 readers
2 users here now
founded 1 year ago
MODERATORS
Thank you!
Hey @jerry, looks like it's stuck again. Been 3+ hours it looks like.
It's working through the backlog now. Another obscure bug in an incoming message that stopped message processing.
@[email protected] Yep, same problem for me, someone needs to message Jerry
I've sent him a DM on infosec.exchange (Y)
Edit: he said he's taking a look
yep, just posted the issue to github about 42 minutes ago, maybe somebody kicked the instance?
Interesting choice over there to close the issue so quickly rather than asking for more info, although you didn't give them much to go on.
I wonder what was the resolution of the previous problem that frequently caused this sort of thing? Was the error handling improved such that we might reasonably expect the processing to keep going when it hits something it doesn't like, or was it just a quick fix for the one specific thing that happened to be breaking it at the time? Did that one make it to the github tracker?
That GitHub tracker is for problems with mbin code, not with instances running Mbin software. The problem that Fedia experienced is very likely caused by a bug of some sort in mbin (or something that Mbin is depending on), but we don’t know for sure what it is yet. Once I’m unemployed in a week, I hope to have more time to debug issues like this and get them resolved.
I thought maybe I could help somehow but it turned out I was insufficiently unemployed, for this week at least. Good luck though.
Hello from a different instance.