Finally, the separate box of POWER9 upgrades appears. These are for the dual socket 144 thread Talos II here at home (the LC-922 are in colo). Relocation has turned up a lot of missing hardware, very pleased about this turn of events.

So, the long lost box contains:
- 4x Samsung 883-DCT 2TB SSDs for local storage ZFS pool (with 2x Optane NVMe cache)
- 3x PM863a 240GB SSDs for the OS
- always more RAM
- an OcuLink 4x to U.2 cable w/ Optane drive floating around somewhere
- Mellanox 50GbE QSFP28 NIC for RDMA fun

@dexter finally, we can continue the project with appropriate hardware

#homelab #power9 #ibm #freebsd #goodmorning #unpacking #servers #hardware #happiness

Finally, the separate box of POWER9 upgrades appears. These are for the dual socket 144 thread Talos II here at home (the LC-922 are in colo). Relocation has turned up a lot of missing hardware, very pleased about this turn of events.

So, the long lost box contains:
- 4x Samsung 883-DCT 2TB SSDs for local storage ZFS pool (with 2x Optane NVMe cache)
- 3x PM863a 240GB SSDs for the OS
- always more RAM
- an OcuLink 4x to U.2 cable w/ Optane drive floating around somewhere
- Mellanox 50GbE QSFP28 NIC for RDMA fun

@dexter finally, we can continue the project with appropriate hardware

#homelab #power9 #ibm #freebsd #goodmorning #unpacking #servers #hardware #happiness

Does anyone know what could cause the error "HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2)" or "Stream error in the HTTP/2 framing layer" when using cURL and monitoring? In the browser, this shows up as a blank page or an HTTPS error.

I'm running Nginx and PHP-FPM with FastCGI cache. This issue is new to me, and I have no idea how to fix it. Disabling FastCGI cache completely resolves the problem, which does not solve the underlying cause and of course leads to page not having a caching mechanism like this.

#SysOps#Webserver#Servers

#GeminiProtocol #Fediverse #ActivityPub #servers

#GeminiProtocol #Fediverse #ActivityPub #servers

movers today, homelab racks return. finally. and having 5GbE symmetric fiber is a proper match. let's see... bunch of amd64, various eras of arm64, POWER9 ppc64le, and a Mac G5 PPC-970MP (water-cooled) off-screen...

looking forward to rebuilding the networks 💝

#homelab #freebsd #linux #servers

💾 Vintage Obsession 💾

I've been in love with this one for months, years, decades. Perhaps one day, when the moons align, I'll grab four Pentium Pro "Black Edition" CPUs and as much RAM as its mezzanine cards can handle, and ... well, you know how the rest of the vintage hardware story goes. Beautiful. The only concern is, "wtf is it doing on the EMI static-charged carpet for the photos?"

#vintagecomputing #pentiumpro #pentium #eisa #hardware #oldtech #servers #ebay

Just spent 6 hours trying find out and solve why my Matrix instance is showing: {"errcode":"M_NOT_FOUND","error":"Not found"} when trying to access images. I did not notice this problem before, because Matrix/Element caches images locally using blobs, but realized this after uploading images to IRC via heisenbridge.

I first thought I had messed up my S3 Object Storage. Then thought I messed up my filesystem. Then I thought I made a mistake in yaml configs. But it was none of that.

It's a while since I installed my Matrix server and completely forgot on how I set up my S3 Object Storage. It seems it is literally not documented. Like at all. Just like the half of Matrix and Synapse.

I ended up debugging literally anything and everything without any solution. After turning all stones I even asked ChatGPT and it started to run in loops in despair. Finally ended up reading synapse changelog here one bit by bit: https://element-hq.github.io/synapse/latest/upgrade.html#authenticated-media-is-now-enforced-by-default

It seems, I have upgraded in some point. And wow, in between of upgrades the whole thing has broken. I mean it runs without erros, but it's broken. No deprecated warnings in the log, no warnings in release logs. Left a comment here: https://github.com/element-hq/synapse/pull/17889#issuecomment-2564520513

My solution was to add in homeserver.yaml:
enable_authenticated_media: false

What I hate about Matrix is:

- Nothing is documented
- Nothing is explained
- Everything is complicated to set up

Each upgrade and extension is like building and tinkering for hours and hours and hoping for the best.

I don't know why I keep using Matrix. Guess I like being hurt all the time.

#Matrix#Element#MatrixSynapse#SysOps#Servers#API