September 30, 2025Sep 30 Good morning! I had this error show up a few months ago, but the server seemed to be running smoothly. I rebooted it after the webgui stopped responding and it has been up for 17 days. Woke up this morning to another notification about out of memory and would like to fix it if possible. Could someone help me troubleshoot? Attached is the diagnostics zip. To help me do this on my own next time, could you share what exactly you are looking for in the zip? Thank you.mercury-diagnostics-20250930-0843.zip
September 30, 2025Sep 30 Community Expert Looks like back on the 22nd node ran over its memory limit and was killed, twice. You can allocate more memory to it, or change whatever you were doing to use less RAM. Reboot to clear the log so FCP stops warning youSep 22 21:03:13 Mercury kernel: Memory cgroup out of memory: Killed process 24538 (node) total-vm:1292120kB, anon-rss:48364kB, file-rss:996kB, shmem-rss:0kB, UID:0 pgtables:1536kB oom_score_adj:0Sep 22 21:54:07 Mercury kernel: Memory cgroup out of memory: Killed process 724928 (node) total-vm:1280704kB, anon-rss:37004kB, file-rss:652kB, shmem-rss:0kB, UID:0 pgtables:1276kB oom_score_adj:0
September 30, 2025Sep 30 Author This might be a rookie question, but I'm a rookie 🤣 Is there a way to determine which docker container likely caused this? My VM has been shut down since I rebooted. The machine has 64 GB of memory and typically idles around 8GB so there is a lot of headroom there. Edited September 30, 2025Sep 30 by MooseOnTheLoose
September 30, 2025Sep 30 Community Expert 4 hours ago, MooseOnTheLoose said:This might be a rookie question, but I'm a rookie 🤣 Is there a way to determine which docker container likely caused this? My VM has been shut down since I rebooted. The machine has 64 GB of memory and typically idles around 8GB so there is a lot of headroom there.Whatever container is running node - you can run ps -auxf to figure out which one is kicking it off. It'll be one you have memory limited, since the host itself isn't running OOM, the container is hitting whatever memory limit you have set for it
October 1, 2025Oct 1 Author Solution Running the command ps auxf > processes.txt and then grepping for node using cat processes.txt | grep node -n to show the line number helped track down the possible culprits. EDIT: The problem ended up being easier to find than I thought. The syslog lists the docker container id that caused the memory problem. Thank you @Michael_P for helping track this down. Edited October 1, 2025Oct 1 by MooseOnTheLoose Update for a faster solution to finding the culprit.
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.