To all you lazy lemmys,

Just had an alert that the VM running the primary Lemmy daemon has low memory available.

I'll be taking the opportunity to update Lemmy to 0.19.20, as well as all the frontends.

Brief outage incoming....

Edit: Update complete. And I noticed the update is labelled "reduce memory usage".... doh

Following the fediverse drama surrounding this front-end and subsequent abandoning of the project by its maintainer, this front-end will be retired effective immediately.

The retaliatory malicious code deployed recently didn't help. Latest drama post at https://lazysoci.al/post/51452204

Apologies for the inconvenience.

cross-posted from: https://lazysoci.al/post/50908536

The VM running the Lemmy binary itself is getting close to 90% ram usage. I'm just going to quickly restart and double the RAM.

Update: all done

The VM running the Lemmy binary itself is getting close to 90% ram usage. I'm just going to quickly restart and double the RAM.

Update: all done

cross-posted from: https://lazysoci.al/post/49677471

Hi Lazy Lemmys,

When I first put together Lemmy, I setup Lemmy, nginx etc. as standard apps. I then migrated to Docker sometime after.

I've since then split Lemmy into separate VMs for lemmy-core, database, frontends and pict-rs, all deployed using ansible.

I now want to re-deploy lemmy-core with ansible on a fresh VM.

I'll be performing this migration today (in the next hour or so), but I expect Lemmy to only be offline for about 15 minutes.

Hi Lazy Lemmys,

When I first put together Lemmy, I setup Lemmy, nginx etc. as standard apps. I then migrated to Docker sometime after.

I've since then split Lemmy into separate VMs for lemmy-core, database, frontends and pict-rs, all deployed using ansible.

I now want to re-deploy lemmy-core with ansible on a fresh VM.

I'll be performing this migration today (in the next hour or so), but I expect Lemmy to only be offline for about 15 minutes.

Update: 1st outage of ~5 minutes completed. Just cloning this VM so I can re-use the proxmox VMID on the new VM. One more outage to go...

Final Update: All up and running on the new VM

cross-posted from: https://lazysoci.al/post/49274084

Hi me again, here to ruin your day.

I migrated the S3 storage to RustFS last month, which has been running OK. I have now decided that pict-rs should run on its own dedicated instance of RustFS instead of the current shared one.

Unfortunately the mirror takes about 3 hours to complete. lazysoci.al will be offline until this is completed.

Hi me again, here to ruin your day.

I migrated the S3 storage to RustFS last month, which has been running OK. I have now decided that pict-rs should run on its own dedicated instance of RustFS instead of the current shared one.

Unfortunately the mirror takes about 3 hours to complete. lazysoci.al will be offline until this is completed.

Update: Back online! Took 40 minutes longer that expected as I got bored waiting so went out for a ride :)

Took the opportunity to upgrade Lemmy to 0.19.19

cross-posted from: https://lazysoci.al/post/47764625

We use an S3 back-end for Pict-RS, which hosts thumbnails and cached images. I am migrating the S3 back-end from minio to rustfs.

Minio went rogue, and then they archived their community/FOS version. So I've had a replacement in the form of RustFS ready but have yet to pull the trigger for Lemmy.

I have been doing a regular mirror of the two buckets, which takes just over 2 1/2 hours to complete.

When this post in 1 hour old, I'll be shutting down Lemmy and performing a final migration, so expected downtime is 2 to 3 hours.

Sorry for the outage!

We use an S3 back-end for Pict-RS, which hosts thumbnails and cached images. I am migrating the S3 back-end from minio to rustfs.

Minio went rogue, and then they archived their community/FOS version. So I've had a replacement in the form of RustFS ready but have yet to pull the trigger for Lemmy.

I have been doing a regular mirror of the two buckets, which takes just over 2 1/2 hours to complete.

When this post in 1 hour old, I'll be shutting down Lemmy and performing a final migration, so expected downtime is 2 to 3 hours.

Sorry for the outage!

Update: And we're back!

Just done a quick update of Lemmy to 0.19.18 Also updated front-ends

That is all.

Hoping someone can help here.

WomensStuff was migrated from my instance using piefed migration tools some months ago, however I still get all the reports for their community even though I am not the instance admin, the post/commenter is not from my instance, and the reporter is not on my instance.

Example:

I have reached out to @LadyButterfly@piefed.blahaj.zone and then @ada@piefed.blahaj.zone but got no response.

Whilst WomensStuff has a logical reason, they were migrated from lazysoci.al, I am also receiving the odd report for other communities not associated with us, but every time the reporter is a piefed user. Coincidence maybe?

Another example:

I'm thinking this is a piefed issue, has anyone else had the same problem?