1y ago

Version 0.19.1 outgoing federation issues for anyone else?

Users of lemmy.today are reporting that outgoing federation of posts and comments stopped to work after the update to 0.19.1 about 19 hours ago.

A restart of lemmy software seems to have made it work again for now, but not sure for how long.

In this version its also common with CPU spikes on a regular basis. I assume its the new federation queue that takes more cpu in exchange for being more reliable. But I see a lot of Postgres UPDATE queries that did not occur in previous version. Also sometimes i see ROLLBACK, which I assume should not be happening.

Anyone else has similar issus with 0.19.1?

Relevant thread: https://lemmy.today/post/4382768

8 comments

This post, a day before yours on the !lemmy_support@lemmy.ml community, is describing some similar behavior, with some CPU usage at start (at least on the first boot; not clear whether that is a one-off on migration from the text) and then federation problems with 0.19.1:
https://lemmy.ml/post/9563852?scrollToComments=true
After upgrading Lemmy from 0.18.5 to 0.19.1, the lemmy_server process is taking up 200-350+% of my CPU....It seems like my instance isn’t federating properly now tho.
- Yeah that's what we are having here too, huge cpu usage and issues with outgoing federation. Sounds spot on.
- I got som weird behaviour, like nothing worked very well, with 0.19.0 so I updated to 0.19.1 and after quite a while (small instance, beefy PC) it starts to work again, it seems.
  Except I am now a moderator everywhere. Maybe it doesn't work, I won't try, except asked, so can someone make a post that I can sticky or delete just to see what's happening?
  Cheers!

I was having issues with outgoing federation to Mastodon on 0.19.0. I just did the update five minutes ago, so we'll see if that fixes it. If you're seeing this comment I guess it's working at the moment.
- What we are seeing is that outgoing federation of posts and comments works after a restart, but new posts and comments made on the local instance are not federating to other instances until the next restart. This is with version 0.19.1.
  Also after a restart, the server eats a lot of cpu for several minutes. Im guessing this is normal with the federation queue being processed but cant be sure.
  
  Good to know; thanks! I’ll keep an eye on it.

Yeah. Had the problems with 0.19.0. Thought it was fixed with 0.19.1. But I guess it was just the restart that fixed it temporarily. Now I've got to remember to check every now and then if my comments federated.

I‘m on 0.19.3 I think. 0.19.1 caused a ton of issues is why people suggested to immediately upgrade iirc. Would probably upgrade asap.

8 comments