Linux processes

It was little Bobby Tables

Middle name Drop

Alright who's running the database on the same machine as the server...👀

If you can do this, do it. It's a huge boost to performance thanks to infinitely lower latency.
- And infinitely lower reliability because you can't have failovers (well you can, but people that run everything in the same host, won't). It's fine for something non critical, but I wouldn't do it with anything that pays the bills.
Most beginner selfhosters.
- and most every cpanel (and every other web host panel) box on the planet.
  web, ftp, database, mail, dns, and more. all on one machine.
For distributed that feed back to a centralized DB? Me. All the dang time.
I'm not that brave doing development by connecting to Production database

Ok, now I need a 8 season animated show and at least 2 direct-to-TV movies of this

Best I can do is a Netflix series that gets cancelled halfway through season 2 and a fan-made animation spoof on YouTube
- As long as the animation is done by Don Hertzfeldt, you have yourself a goddamn deal!
- I am in.

Fuck MySQL, all my homies hate MySQL.

Postgres is the way to go.

"MariaDB"
- Yes, Maria too.
  Postgre is the way
- I'm not sure what the future of MariaDB is... It lacks a bunch of newer MySQL features, and they've deviated far enough that I don't know if they can cleanly backport them from MySQL any more.
It was you! You killed it.
- I do admit to moving the company cluster from MySQL to Postgres.
  But only most of the traffic, some traces still remain, so the original MySQL still works
- I did two rounds of very long presentations comparing those two systems.
  Personal reasons:
  SQL standard support is still very weak
  lack of WAL
  array support
  weird replication support
  utf8mb4 mess took too long to resolve
  many things started to get better only after Oracle takeover
- Because it's proprietary

Random guess, a php error caused Apache to log a ridiculous number of errors to /var/log and on this system that isn’t its own partition so /var filled up crashing MySQL. The user wiped /var/log to free up space.

That's not far off of something that happened to me once a few years ago. My computer suddenly started struggling one day, and I quickly figured out that my hard drive suddenly had 500 gigs or so of extra data somewhere. I had to find a tool that would let me see how much space a given folder was taking up, and eventually I found an absolutely HUMONGOUS error log file. After I cleared it out, the file rapidly filled up again when I used a program I'd been using all the time. I think it was Minecraft or something. Anyway, my duck tape solution was to just make that log file read-only, since the error in question didn't actually affect anything else.

Plot twist: it was the user

That's not even a plot twist, that's expected user behavior

All evidence point to suicide.

I hadn't realized this was a .ru domain....
- Maybe it's a 'Windows' server...

Systemd. SQL is now in Systemd.

Dont spoil. That's the secret in Episode 5.

I understand none of this.....

"Among us" but for Linux nerds.

It looks like the OOM killer has struck again.

It was Java, coaxing the Linux OOM killer into doing the job

This process has been murdered mysteriously.

Oracle.

/var/log has been deleted, you say...

I think we all know what this means, don't we?

- I have no clue. Root nuked the logs? Why? OOM killer does not do that.
- That seems so obvious I think we're missing something

Will there be a follow up?

I did it like this: 🔫 BANG WhooOooOoopty doOoO

It was the kubelet after MySQL failed his liveness probes

Like everytime with natives, it was a race condition cascade of table locks followed by mysql suicide caused by bad cronjob scripts implemented by the user.

So... bash ?

It was the BOFH

It was taking away resources from the coffee cam. Had to go.

Mariadb did it with the candlestick in the library.