Hi all,

We were getting several reports of people linking to csam content in the signal groups community. We tried to contact the moderator but no response in several days.

Its difficult to moderate this kind of content. Moderators of a lemmy community cannot be expected to visit each posted group around the clock to make sure it doesnt have csam content. Signal groups can change their content at any time.

So sorry to say, it had to be removed. If you were using it, I hope you find some other way to find new signal groups.

We decided to double the server memory and add more cpu, since we were close to running out sometimes.

So if you notice higher performance, you know what the reason is now. :)

Short post, but just wanted to mention it.

We just deployed the latest version of Lemmy 0.19.2 where the github code includes a possible fix for the outgoing federation issues we have been having.

But lets see before we celebrate. Help us test if outgoing federation seems to work now by making comments, posts and upvotes and see if they appear on other instances.

Of course if the other instances are on Lemmy 0.19.0 or 0.19.1, they could have issues with outgoing federation still until they update.

Release notes for 0.19.2: https://join-lemmy.org/news/2024-01-10_-_Lemmy_Release_v0.19.2_-_More_Federation_Fixes

Please try to comment and post things now, and see if they federate again.

Hopefully you see your activity instantly federated. I have tried making comments both to instances running Lemmy 0.19.1 and 0.18.5 and they all federate like they should.

Hope you have the same experience! 🥳

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. :)

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

Today we spent some time preparing for the big upgrade, by kicking the Lemmy version up to 0.18.5, merging in the latest changes from lemmy-ansible git repository and cleaning up some disk space on the instance.

So tomorrow at 02.00 am Oregon time we will do the update to Lemmy 0.19.

This is 11.00 am CET for people in Europe.

Hopefully all goes well and we come out the other side with a nice new 0.19 version. Its supposed to take about 30 minutes of downtime if there are no issues to solve.

Wish us luck :)

IMPORTANT: You probably need to log out and log in again to be able to post anything since they reworked authentication in this release.

Hi,

We are planning to install Lemmy 0.19 soon, hopefully in the coming week or so. It's a huge release with many new features, and I personally really like that it allows you users to block other instances if you want to.

You can read about all the new features in the link above.

More info coming in a few days about planned downtime and so on. :)

We just had another unscheduled downtime due to a linux kernel bug.

Yesterday we noticed some issues with the server - mainly that we couldnt stop some docker containers. As you know, we are running some extra user web interfaces for Lemmy and we noticed that they started acting weirdly and had one cpu running at 100% constantly.

I wanted to restart those containers but I couldnt stop them. Found some posts online that this is a bug in the Ubuntu linux kernel: https://github.com/moby/moby/issues/43094.

Our stop attempts caused the docker platform to behave weirdly and it started to affect the main Lemmy software, so we did a reboot of the server and installed the latest updates.

We are very sorry for this unscheduled downtime. :/ Did you guys notice weirdness with Lemmy in the last 8 hours or so?