My server (fedora) stops all podman containers after 2-3 hours since 3 days. I can start all containers again, and the same happens after a while. I do not know where to look for the problem.
In top, I found a oom message. I assume that the system runs out of memory and stops all services. How can I find the problem? I can’t find anything in the container logs.
I can see that systemctl status is always starting. It doesn’t become “running”. But I do not know how to proceed.
The issue with diagnosing memory issues is that it usually results in no memory available to handle the logging of such a problem when it happens.
I’ve found that the easieat approach is to set up a file as additional swap space, and swapon, then see if the problem disappears, either partially or fully.
I’ve got way too much RAM for swap being useful at all. Good idea though.
There is no such thing as too much RAM…
If something you’re running has a memory leak then it doesn’t matter how much RAM you have.
You can try adding memory limits to your containers to see if that limits the splash damage. That’s to say you would hopefully see only one container (the bad one) dying.
that’s neat. Tank you.
So far I follow a bottom up strategy. I’ll keep adding containers each day (or after many hours) and wait for it to stop. I also looked up how to limit memory usage. It’s a great idea to limit all containers and see which one fails. thanks!
How do you know that you have too much ram? Have you set up a monitoring solution like influxDB to track ram usage over time?
I observed it during resource hungry usage. I never had issues with it, not even close.
Then you didn’t understand how the system uses swap.
https://chrisdown.name/2018/01/02/in-defence-of-swap.html
They could mean that they have swap but it’s not being used.
I’m just curious how much RAM you think that is.