Michael_P

It could be choking on a bad file while it does its media scan, if you have added new items check those first. The plex log might be helpful too as the last thing it was doing would be in there

Whatever container matches this id: 8a019cf493fc had a chrome process run away. Reboot to clear the log so FCP stops warning you about the past event.

FCP doesn't "confirm" anything, it just looks at the syslog for any lines with the phrase 'out of memory' and triggers the alert.

Reboot to clear the log so FCP stops warning you about the previous event

Yes, you can find them on the dockers tab and toggling advanced view, this will show their IDs. It keeps coming back because you have a memory limit set for those containers, and they are hitting it. You can either ignore the error reports (FCP will always warn if it sees "out of memory" in the log regardless of the reason) or change the limits in the extra parameters. For Example:

Both of the MCEs were corrected errors with no action required, so just reboot to clear the log so FCP stops warning you

looks like your AI app is running the host OOM - either fix its config or add more RAM (16G is a bit light for AI work), then reboot to clear the log so FCP stops warning you

The host is running OOM and killing the VM everyday at midnight, either add more RAM or take some away from the VM

Jellyfin is hitting the limit you set for it so it's being killed - you will need to reboot to clear the log so FCP stops warning you

Your OOMs are your containers hitting their limits repeatedly (a05c024d27aa and 2cdd63857d4) You'll need to adjust the amount they're allowed or configure them so they don't use more than the amount you've set. You'll need to re-boot to clear the log so FCP stops warning you, once you've fixed the containers.

Every time one of your containers hits the limit it will be culled and logged, which FCP will detect and report every single time FCP scans the log, so you will need to reboot every time to clear the log. You can use the advanced tab to match the first 12 digits of the container ID'd in the log ie:

Immich is running the host OOM, 16GB is a little light if you want to run it with all of the rest of your services - you can try to tune it a bit or limit the RAM to the container but you should probably just add more RAM. When you've fixed or disabled Immich, you will need to reboot to clear the log so FCP stops warning you about it

Looks like on the 2nd and 18th of June Plex media scanner hit its memory limit and was killed. You can check the container logs to see if there's a file it doesn't like. Reboot to clear the log so FCP stops warning you

If it does it again, run ps -auxf > ps.txt from the command line and that should show you what's using it. Navigate to a folder share first so you can grab the ps.txt that it generates

Only if they ship it DDP, else it's on the IOR