Announcements

242 readers

1 users here now

Announcements about system updates or other things related to this instance.

founded 1 year ago

MODERATORS

[email protected]

Outgoing federation issues (lemmy.today)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

19 comments fedilink hide all child comments

As you may have read in other threads, this version of Lemmy (0.19.1) seems to have bugs in outgoing federation on some instances.

As a temporary fix, we have added a scheduled restart of Lemmy every hour. It only takes a few seconds to restart, and the big advantage is that your comments and posts are only delayed up to 1 hour before they federate to other instances. You probably wont notice the restart even.

This will be in effect until a bug fix arrives from Lemmy developers, probably after new years sometime.

Thanks for reading and merry x-mas to everyone. :)

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago (2 children)

Yes, it seems the restart is not as reliable as I was hoping for.

Its a docker compose restart of the entire stack but that has proven to work only sometimes, which is not good enough. This afternoon it failed once (as you noticed), then worked 4 times, then failed once more.

We will figure out a more reliable way to restart, but for now, the restart has been removed again.

Really sorry about all this. Just trying to find a way to make federation work again since its very frustrating when it doesnt.

Anyway, merry Christmas and thanks for being understanding during all this.

[–] [email protected] 3 points 1 year ago (1 children)

For what it's worth, I set up a cronjob on my instance to restart just the lemmy container every 6 hours. It looks like 0 */6 * * * docker container restart lemmy-lemmy-1. Federation has been pretty good so far, but it has only been in practice for less than a day.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Yeah I could try to restart only the Lemmy container instead of the entire stack. Worth trying, thank you. :)

I tried it and it does give 20 seconds of downtime but could be worth doing a couple of times per day anyway. Its so frustrating with no outgoing messages...

[–] [email protected] 3 points 1 year ago (1 children)

We must have all been very naughty this year for Santa to bring us this heap of bugs. :/

[–] [email protected] 2 points 1 year ago (1 children)

Hehe indeed. :)

[–] [email protected] 1 points 1 year ago (2 children)

Sadly, even with the scheduled restarts it seems like only about half of my posts and comments make it out to other instances.

[–] [email protected] 3 points 1 year ago (1 children)

We had to remove the scheduled restarts since they didn't work reliably and brought the server down. So they are not in effect right now. We do manual restarts a few times per day only.

Still hoping for a fix from Lemmy devs soon...

[–] [email protected] 3 points 1 year ago (1 children)

Well, at least it appears that they are aware of the problem, and one guy said he may have found a fix for it. There is a pull request open that might fix it, so hopefully, this'll be over soon.

[–] [email protected] 2 points 1 year ago

That sounds awesome. I really hope it fixes the problem, this is so frustrating. Thanks for the links!

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

As far as I can tell, not one of my comments has made it out in the last 4 days. No replies, no votes, not visible on any instance outside of lemmy.today.

Such is life on the bleeding edge...

Edit: seems like at least some got pushed out, as I'm finally getting responses again.

[–] [email protected] 2 points 1 year ago

Everything is pushed out but only when we restart the server... Hopefully a fix for that soon!