@hitstun@fedia.io @jerry@fedia.io @Nougat@fedia.io hopefully you’ve seen my other messages on Fedia. I think I’ve fixed the problem by deleting /m/fediverse and purging the backlog of deliveries. The threads mentioned above were delivered but due to the issues with /m/fediverse (and possibly /m/random) the server was running way behind because it was spending all its time retrying deliveries that would never be accepted by other instances. Sadly I think I’m going to have to leave /m/fediverse deleted till the underlying mbin bug gets fixed.
jerry
joined 7 years ago
@hitstun@fedia.io @jerry@fedia.io @Nougat@fedia.io it got here. I will go check.
@Fitik@fedia.io I removed the block. I’ve been having some luck in reducing the server load today with the help of the mbin team.
@Fitik@fedia.io messages to/from threads has been causing some major problems with the message processing queues on fedia.io. To keep the instance running, I had to block it until I can sort out why.
@IlliteratiDomine @DarkThoughts I found the problem - it was an error I introduced when moving fedia,io to containers recently. it works now.
@IlliteratiDomine @DarkThoughts Thanks for tagging me. I wasn't aware there was a problem. I'll take a look.
Hello everyone. If you care about fedia.io, please read this: https://fedia.io/m/fedia/t/350673
Note: it’s good news-ish
@liaizon @geekgrrl @fediverse agree. I haven’t played with it much, but it seemed a lot further ahead than WF
@geekgrrl @liaizon @fediverse sadly Plume is dead - and I fear that writefreely is also dead software walking. I will have to look at the others...
view more: next ›
@Nougat@fedia.io @jerry@fedia.io @hitstun@fedia.io I had to remove /m/test too, and now the delivery queues are holding at zero, as they should be.