Hello,
I had a memory issue with one of my process running on a LXC container.
It seems like one of my Java process has taken too much ressources (which can unfortunately happen). In consequence, I was expecting the Java process to be killed because of OOM. But it didn't happen and so my container had completely frozen. I had to kill the container because I was unable to access it.
Does anyone know why in this situation the OOM Killer has not been triggered ?
Is there something I can change in my configuration so the container can kill processes when exceeding the allocated memory ?
I have also noticed that the command "dmesg" does not work anymore on my containers since I have updated Proxmox from 5.4 to 7.2.
Thank you in advance if you can help me.
I had a memory issue with one of my process running on a LXC container.
It seems like one of my Java process has taken too much ressources (which can unfortunately happen). In consequence, I was expecting the Java process to be killed because of OOM. But it didn't happen and so my container had completely frozen. I had to kill the container because I was unable to access it.
Does anyone know why in this situation the OOM Killer has not been triggered ?
Is there something I can change in my configuration so the container can kill processes when exceeding the allocated memory ?
I have also noticed that the command "dmesg" does not work anymore on my containers since I have updated Proxmox from 5.4 to 7.2.
Thank you in advance if you can help me.