I remember this being in the news, but didn't have enough time or interest at the time to pay attention.

Interesting story!

Wanted to let it out

Got a good chuckle out of it :)

All on my own!

I've heard horror stories about it taking months upon months in the past and they've been keeping me from trying. Silly me :)

It took under two days; and most of the time was trying to figure out all the problems caused by being behind a an http proxy. Looking back, I can see it can be done in a minute or so now that I've got a few bits of config nailed down.

Granted this is a very bare bones cluster atm, but applying that test nginx deployment and seeing all three replicas running, one on each node, has sent me buzzing :)

Next step - generating an internal intermediate and shoving it into the cluster.

Happy Monday!

Archive link

It appears Trump is going to be the next president of US. I'm not sure such a thread is needed in the first place, but here goes.

Feeling anxious? Desperate? Got the expected result?

What do you think went wrong? What do you think went right? What do you think the future holds?

EDIT: it's official - https://www.bbc.co.uk/news/election/2024/us/results

Sorry for causing all the inconvenience

Bloody solarwinds

Leaving a builder account enabled after build has completed is a fairly big oversight.

Everything went through smoothly, but please do report if you notice anything.

Lemmy Cafe will be having its database upgraded.

Reasons

• PostgreSQL 17 has been released and the changelog is promising a lot of IO improvements. Lemmy sure could use it given the constant stream of small events flowing in.

Plan

• Point nginx to the maintenance page
• Shut down PostgreSQL 16
• Run the upgrade tool
• Start up PostgreSQL 17
• Point nginx to lemmy

Expected downtime

About an hour, if things go well. More if not so.

Will try to keep the maintenance page updated.

Here's the timezone converter.

Manners maketh man.

This does imply a cups server being open to the internet or an already breached network.

3.6 roentgen.

Hey, we own a few thousand of those! Oh, wait...

Might be a long few days coming 😮‍💨

There used to be a www-apps/jellyfin, but it is now gone. Anyone heard of a reason?

Admittedly, I have a fairly serious bias against Microsoft, so it's unlikely they'll every say much I can trust; but I am genuinely surprised their marketing department didn't even bother coming up with another name to try selling this atrocity.

Due to the recent @Soup's post I have decided to do some housekeeping. I've been getting frustrated at lemmy's performance at times as well and this simply was a wake up call, if you will.

I am sorry about no advance downtime annoucement - Sunday is the only day I can really put any meaningful amount of time into lemmy.

Things done today:

• Upgraded database VM 1 core 2GB -> 2 cores 4GB. Double the compute, double the memory.
• Adjusted database config to account for increased resources
• Adjusted hugepages config to account for increased database's requests
• Updated both lemmy and database VMs
• Rebooted the lot

Thank you for your patience. I will also use this moment of focus to write up a financial report in a separate post.

Also, thank you, @Soup!

EDIT: I've also marked all instances known to lemmy.cafe as active. What this means is that lemmy.cafe will now keep retrying to federate to everything very aggressively. This is a compute-intensive process and will also impact performance for a few hours, until exponential backoff kicks in. I've done it to revive any falsely-marked-as-dead instances; there's no fix for it on lemmy itself.

The company I'm at right now is on this boat as well

Archive link