carotna Posted May 16 Share Posted May 16 (edited) Hi all. After a few days I am getting the Out of memory error in the syslog and the docker service to stop (all apps down) I post here the logs before rebooting if someone can help me. Thank you. I currently have 32GB RAM in the server with only 1 VM with 2GB of RAM assigned. The rest Docker containers. kernel: Out of memory: Killed process 12305 (dockerd) tower-diagnostics-20240516-1157.zip Edited May 16 by carotna Quote Link to comment
JorgeB Posted May 16 Share Posted May 16 Jellyfin appears to be the main problem, try limiting its RAM usage, but also see tens of docker-proxy processes, which are not using many RAM, but that doesn't look normal. Quote Link to comment
carotna Posted May 16 Author Share Posted May 16 Hi, ok will try with --memory=2G for example? Also, for the proxy processes, I don't really know any I installed. Do you mean like installing proxies? Sorry about the question. Quote Link to comment
JorgeB Posted May 16 Share Posted May 16 53 minutes ago, carotna said: ok will try with --memory=2G for example? Yes, or 4G. 53 minutes ago, carotna said: I don't really know any I installed. Do you mean like installing proxies? Sorry about the question. They should be related to one of the containers you are running, try just limiting the RAM for Jellyfin for now, also, I think you should also check that you are not transcodig to RAM. Quote Link to comment
carotna Posted May 21 Author Share Posted May 21 Hi @JorgeB, sorry, it is freezing again, would you please like to help? Here's today's logs. tower-diagnostics-20240521-1853.zip Quote Link to comment
JorgeB Posted May 21 Share Posted May 21 Docker daemon itself got killed because it was using a lot of RAM, still seeing a lot of docker-proxy processes, but don't know which container is creating them, you will need to try and find out which container is causing the issue, unless someone else has a better idea, you can try running half of them, if the issue remains try the other half, then keep drilling down. Quote Link to comment
carotna Posted May 21 Author Share Posted May 21 5 minutes ago, JorgeB said: Docker daemon itself got killed because it was using a lot of RAM, still seeing a lot of docker-proxy processes, but don't know which container is creating them, you will need to try and find out which container is causing the issue, unless someone else has a better idea, you can try running half of them, if the issue remains try the other half, then keep drilling down. OK, sorry but where do you see the proxies? in what log? Thank you, will try the half-half method. Quote Link to comment
JorgeB Posted May 21 Share Posted May 21 Look in the syslog-previous, when there's an OOM event, it list all the running processes, and there are tens ( or hundreds) of these: May 21 05:43:45 Tower kernel: [ 30171] 0 30171 177706 572 81920 0 0 docker-proxy May 21 05:43:45 Tower kernel: [ 30179] 0 30179 177770 571 77824 0 0 docker-proxy May 21 05:43:45 Tower kernel: [ 30193] 0 30193 177706 571 77824 0 0 docker-proxy May 21 05:43:45 Tower kernel: [ 30200] 0 30200 177706 572 77824 0 0 docker-proxy May 21 05:43:45 Tower kernel: [ 30214] 0 30214 177706 574 77824 0 0 docker-proxy May 21 05:43:45 Tower kernel: [ 30221] 0 30221 177706 570 77824 0 0 docker-proxy May 21 05:43:45 Tower kernel: [ 30234] 0 30234 177706 570 81920 0 0 docker-proxy May 21 05:43:45 Tower kernel: [ 30242] 0 30242 177706 573 81920 0 0 docker-proxy May 21 05:43:45 Tower kernel: [ 30255] 0 30255 177706 572 81920 0 0 docker-proxy May 21 05:43:45 Tower kernel: [ 30262] 0 30262 177642 571 73728 0 0 docker-proxy May 21 05:43:45 Tower kernel: [ 30275] 0 30275 177770 572 81920 0 0 docker-proxy May 21 05:43:45 Tower kernel: [ 30283] 0 30283 177770 570 73728 0 0 docker-proxy May 21 05:43:45 Tower kernel: [ 30297] 0 30297 177706 571 81920 0 0 docker-proxy May 21 05:43:45 Tower kernel: [ 30304] 0 30304 177770 570 81920 0 0 docker-proxy May 21 05:43:45 Tower kernel: [ 30317] 0 30317 177706 573 77824 0 0 docker-proxy May 21 05:43:45 Tower kernel: [ 30323] 0 30323 177706 571 81920 0 0 docker-proxy This is not normal. Quote Link to comment
Michael_P Posted May 22 Share Posted May 22 14 hours ago, JorgeB said: This is not normal. 14 hours ago, carotna said: Thank you, will try the half-half method. Start with the container using this IP, it's the one opening a ton of ports -container-ip 172.18.0.11 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.