OOM OOM

[SamTzu]

 kernel: oom-kill:constraint=CONSTRAINT_MEMCG,nodemask=(null),cpuset=ns,mems_allowed=0,oom_memcg=/lxc/602,task_memcg=/lxc/602/ns/system.slice/mariadb.service,task=mariadbd,pid=3269753,uid=100108

My ISPconfig server wont restart any services that have been OOM killed.
I'm thinking this is probably settings issue in Proxmox LXC container?
What must I change in LXC config to get OOM killed services to recover?

 

[LnxBil]

you need to provide more information, e.g. current container config and settings for maria db

 

[SamTzu]

Everything on the LXC containers is default except 'nesting' is enabled.
Debian is default '12' CT template from Proxmox built using this 'Perfect Server' guide.
And the problem is not just with MySQL OOM-Kills but with any service that should restart but does not.

 

[Kingneutron]

If it's getting OOM killed, you probably need to start by giving it more RAM - it doesn't have enough to run stably with current allocation

 

[SamTzu]

They have plenty.
The current problem child has 4Gb but usually only uses 1Gb.

 

[Kingneutron]

You're probably going to have to start checking SAR logs and setup monitoring in the VM for RAM+Swap usage