#TeeHee #HAHAHAHAHAHA

The #lovely people of #Meriadoc on the #fabulous #LordOfTheRingsOnline have been #polled and #drumroll...

they do NOT want #PocoPsirens to return to the game

#Oopsie #KeepTheVerminOut...

#infosec #cisa #oopsie

https://gizmodo.com/the-worst-leak-that-ive-witnessed-u-s-cybersecurity-agency-leaves-its-digital-keys-out-in-public-on-github-2000760330

RE: https://burningboard.net/@Larvitz/116584334811849567

Post-mortem from today’s FreeBSD/arm64 outage of my prod web-server:

After reboot, the box appeared to hang around ZFS root/init. Pools imported fine from live media, /sbin/init was valid, old kernel/BE made no difference. There was also a stale GPT signature on a whole-disk ZFS vdev, which made the trail extra noisy.

Actual RCA: a stray " in /etc/rc.conf in my static_routes line. rc.conf is shell, so that broke early boot badly enough that networking never came up and it looked like kernel/ZFS/init trouble.

Fixed syntax, restored ZFS canmount values, jails back online.

Lesson: always run sh -n /etc/rc.conf before rebooting. 🫠

#freebsd #outage #runbsd #oopsie

Mastodon Incident Report / Root cause analysis:

Earlier today, users experienced timeouts with Search, Hashtags, and Autocomplete.

Root Cause: Our setup separates the Mastodon frontend VPS (Hetzner) from backend services (for example Elasticsearch) via an OPNSense firewall. Suricata (our IPS) triggered a false-positive on internal traffic and aggressively blocked the VPS IP, severing the connection to the search database.

Resolution: We identified the false-positive, added the frontend IP to the whitelist, and traffic immediately normalized. Everything is back to green!

#mastodon #mastoadmin #burningboard #elasticsearch #firewall #opnsense #suricata #oopsie

BBC: Trainee driver crashes bus into River Seine

https://www.bbc.com/news/articles/cm2pyxpwmdro

#oopsie