-
Does cloudron use the vault process? If so has anyone else noticed that process running out of memory and getting killed by oom? Im getting a "memory cgroup out of memory" warning then process (vault) always getting killed.
-
Is the server itself doing fine on memory? You can check
free -moutput on the server. In addition, do you see oom killing indmesgoutput?@girish yeah server has plenty of memory. I have vault installed but I'm not actually using it yet so I'm unsure of why it's running out of memory. It's definitely getting oom killed though. I get the warning and it shows up in logs. Could it have a memory leak?
Weird thing is it seems to not eat up any server memory just I guess wgats assigned to its container? I still have plenty of free, and cache . Like multi gb worth. -
Is the server itself doing fine on memory? You can check
free -moutput on the server. In addition, do you see oom killing indmesgoutput? -
@girish my Ossec agent first picked up the log , then I started watching it and very soon after reboot it will throw that warning and get oom killed.
@mastadamus I will bump up the memory limit for vault. https://learn.hashicorp.com/tutorials/vault/reference-architecture says 4-8GB is recommended. Currently, the cloudron package runs at 256MB!
Also, as you guessed, it's only the vault container that is dying and the server is not affected (I guess that's one of the main benefits of running in containers, a single app cannot bring down a system).
