Page MenuHomePhorge
Create Task
Maniphest T202

Make kloud a bit more robust
Open, HighPublic
Actions

Description

Perhaps it's because now it's actually being used by more than me, perhaps it's due to changes with T189: Upgrading kloud (the OOM killer is a lot more aggressive by default in newer *buntu versions), but this is not ideal:

image.png (378×1 px, 352 KB)

Certainly there is uhh not that much RAM:

               total        used        free      shared  buff/cache   available
Mem:           957Mi       204Mi        57Mi        14Mi       695Mi       574Mi
Swap:          1.5Gi       104Mi       1.4Gi

but, still...

Related Objects
Search...

StatusAssignedTask
Restricted Maniphest Task
 OpenkeithzgT189 Upgrading kloud
 OpenkeithzgT202 Make kloud a bit more robust

Event Timeline

keithzg created this task.Tue, Nov 12, 6:36 PM
keithzg triaged this task as Unbreak Now! priority.
keithzg created this object with visibility "Public (No Login Required)".
keithzg added a comment.Tue, Nov 12, 6:38 PM

https://mariadb.com/kb/en/systemd/#configuring-the-systemd-service led me to doing this:

/etc/systemd/system/mariadb.service.d/dont-taze-me-bro.conf
[System]
OOMScoreAdjust=-999

That's literally 1 before it would just never kill any processes owned by the database service, which seems like a good moderate choice!

Rebooting now . . .

keithzg lowered the priority of this task from Unbreak Now! to High.Tue, Nov 12, 6:44 PM

The conf got loaded on reboot, so in theory it's all good, but I should perhaps give it some more swap or RAM (and probably disk space?)

keithzg added a comment.Sun, Nov 17, 8:08 PM

... it's still OOM-killing the mariadb service

Macro tableflip_princess-bubblegum:

keithzg added a comment.Mon, Nov 18, 3:30 PM

Looking at the logs, I got the section name wrong. So I've changed it to:

/etc/systemd/system/mariadb.service.d/dont-taze-me-bro.conf
[Service]
OOMScoreAdjust=-1000

But then, I tried rebooting the server and the webserver itself got OOM killed shortly after boot!

1GB is a paltry amount of RAM, so I've bitten the bullet and set to oay the extra mere $6 a month for 2GB RAM on Kloud. Maybe that'll be enough to avoid this problem altogether...