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.
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.
I'll open the back up. An issue with mbin is that there's no way to moderate new accounts, and so I have been battling massive amounts of spam, and the moderation interface for mbin is not super efficient, so it creates a LOT of work.
Report at least one of the posts from any spam account you see. I try to suspend and delete them as I see them, but alas I am not omniscient and don’t know where all the spam accounts are
ok - just looked through logs and I am not seeing anything that looks related to this issue. There are a good number of error 500's coming from kbin.social, but none appear to be around the time of these posts, nor associated with the referenced magazine.