The fix things said to post this here, overall the RAM usage doesn't look wild to me. Which of these log files helps you help me? I started perusing, but didn't find much of anything useful in the few files I checked.

Most memory intensive application is frigate. Almost all my docker containers are restricted to the RAM amount I specify, except some newer containers like paperless-ngx and redis. Frigate is allowed 20gb and is currently in at 16gb. Most of my cameras are running higher detection resolutions (and I have many) so this is expected, not misconfigured.

Finally, why isn't there protective code in the Unraid OS? 99% of my issues would probably not be an issue if UnRaid would just kill things like docker if it was getting out of hand. Even better if it specifically kills a container with a log entry. Even better if there weren't 2-3 places to find the logs. It just baffles me that UnRaid doesn't protect itself, it just seems to go down with the ship.

uhive-diagnostics-20260720-1009-outofMemory.zip

What likely happened is there was many docker containers using RAM in high quantities which resulted in 99% RAM use on the system when that error was generated.

17 minutes ago, moka939 said:

It just baffles me that UnRaid doesn't protect itself, it just seems to go down with the ship.

Did unraid crash? I see there was a reboot since the logs start on July 19th but I cant tell if that was due to a hard shutdown or you just rebooting it.

In this instance, no, no crash, just noticed the indicator in fix common probs. The 19th would've been a crash, for certain. You say "likely" so does that mean there isn't anything in the logs to prove that happened? It could've been an OS memory leak just the same?

23 hours ago, MowMdown said:

What likely happened is there was many docker containers using RAM in high quantities which resulted in 99% RAM use on the system when that error was generated.

Did unraid crash? I see there was a reboot since the logs start on July 19th but I cant tell if that was due to a hard shutdown or you just rebooting it.

And also, does setting RAM limits not prevent it from consuming the full memory on the system? Some of my containers are only allowed 512mb, I'm pretty intense with the limiting.

The OOM event was apparently caused by a Docker container that had a hard memory limit of 768 MB, and it reached it exactly, it wasn't a system-wide out-of-memory event.

Looks like this one: docker/b7215cfc67841485fb9a58cbb88ebde431e9206868bcc0364923718121f566c8

17 hours ago, moka939 said:

I'm pretty intense with the limiting.

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:

b7215cfc6784