November 12, 2025Nov 12 Been experiencing intermittent server crashes and this is really my only clue that something is wrong. Syslog doesn't seem to show anything relevant. I tried putting the hungriest containers on a diet, but it's still happening. Seems to only happen overnight when I have parity check running which is almost every night since the crash triggers another one to start when I boot.Thanks in advance for any help ocean-diagnostics-20251112-0003.zip
December 2, 2025Dec 2 Community Expert The killed process was the Sonarr container; it consumed ~4.9 GB, try limiting its RSAM usage.
December 5, 2025Dec 5 Author On 12/2/2025 at 5:20 AM, JorgeB said:The killed process was the Sonarr container; it consumed ~4.9 GB, try limiting its RSAM usage.Thanks, I've done that and now I'll wait and see. How can I see which container it was if it happens again? I've been looking in the syslogs which didn't appear to show anything like that, at least to me.
December 5, 2025Dec 5 Community Expert Search the syslog for "out of memory", it typically identifies which process was killed, and most often that is the one that was misbehaving.Nov 10 09:35:43 ocean kernel: Out of memory: Killed process 28038 (Sonarr) total-vm:9708976kB, anon-rss:4895868kB, file-rss:312kB, shmem-rss:0kB, UID:99 pgtables:11624kB oom_score_adj:0
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.