Michael_P

nothing in /var/log/mcelog ?

What's the MCE log say?

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

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 you Sep 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:0 Sep 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

Check to make sure you didn't bend any pins on the the LGA

Try turning off your deluge container, too - it looks like that's what's running the python process

CPU could be faulty, have you removed it lately?

Figure out which container is running a python3 instance. running ps -auxf can help you narrow it down

If it's only segfaulting with the python script you're running, start there

Looks like your LLM container hit its limit back on the 26th and was killed. Reboot to clear the log so FCP stops warning you

ps -auxf can give you a more granular report

toggle the advanced view in the docker tab, that will show you how much CPU each container is using

Samba shares probably

Depends, remote access for media or just for general file access?

You'll need to reboot to clear the log or FCP will continue to warn you

Your CCTV drive is dying for sure, for the OOM it looks like you've got a lot going on for 32GBs, re-allocate where you can and limit your containers

It's only a warning, you can just ignore it. Also, if your containers are routinely running OOM such that you need to add a limit in the first place, you should consider changing its config so that it's not doing as much work in RAM, or add more RAM.

Looks like syncthing hit the container's memory limit and was killed

Yeah, it'd be one of your containers. In the output, the processes kicked off by the container will be listed in its hierarchy, so wherever you found that python process, follow it up to the container where you can see its ID. Then, on the docker page in unraid, switch to advanced view to show the IDs and match it up. Here's an example from my server showing what my proxy manager is running The part I've highlighted matches the container shown in unraid

Looks like whatever container you have running python 2.64 would be the place to start. If you don't know which one it is, you can run ps -auxf to figure it out

Change the scaling mode in the sidebar for your VNC session

It could be that it's been operating within available RAM the whole time, and then tried to do too much at once. Double check to make sure the cache location is correctly mapped to disk. Also, reboot the server so the log is cleared and FCP stops warning you about the past OOMs

One of your containers is firing off a bunch of ffmpeg processes, so if you have one that's converting media then change its config so it caches to disk instead of RAM

And make sure to reboot, or FCP will keep warning you about the OOMs that have already occurred

Tdarr is hitting the memory limit and is being killed. Either switch to transcoding to a disk, or reduce the number of simultaneous transcodes