A few days ago, I noticed my Nginx docker container had stopped with an out of memory error. Then, this morning "Fix Common Problems" notified me about it again, suggesting I post here. My Diagnostics are attached, and any help would be greatly appreciated.

unraid-diagnostics-20250727-1112.zip

19 hours ago, d_freshmaker said:

A few days ago, I noticed my Nginx docker container had stopped with an out of memory error. Then, this morning "Fix Common Problems" notified me about it again, suggesting I post here. My Diagnostics are attached, and any help would be greatly appreciated.

unraid-diagnostics-20250727-1112.zip

I don't see any OOM events in your log, but it looks like one of your containers is flapping - check the container list and whichever one has the lowest uptime is the one turning on and off repeatedly.

If you've already solved whatever OOM event FCP is warning you about you can reboot to clear the log so FCP stops warning you, else post the log with the event showing

Sorry if these are dumb questions. I'm rather new to this, and everything I know I've picked up from Youtube tutorials and random Google searches.

The syslog shows an out of memory event with the timestamp Jul 22 14:46:30. If that isn't it, what should I be looking for?

At the time of that event, my nginx container stopped and I had to restart it. Thinking it was that container that ran out of memory, I tried fixing it by adding the Extra Parameter below, but have no idea if that fixed it (or was even the right thing to do).

After I added that parameter, the message below was shown, so I don't even know if it did anything.

Also, what is flapping?

2 hours ago, d_freshmaker said:

Sorry if these are dumb questions. I'm rather new to this, and everything I know I've picked up from Youtube tutorials and random Google searches.

The syslog shows an out of memory event with the timestamp Jul 22 14:46:30. If that isn't it, what should I be looking for?

At the time of that event, my nginx container stopped and I had to restart it. Thinking it was that container that ran out of memory, I tried fixing it by adding the Extra Parameter below, but have no idea if that fixed it (or was even the right thing to do).

After I added that parameter, the message below was shown, so I don't even know if it did anything.

Also, what is flapping?

At that timestamp someone ran a search for that term and it posted in your syslog, FCP will alert anytime it sees the string 'out of memory' in the log, which is why it warned you.

Jul 22 14:46:30 UNRAID sudo: root : TTY=pts/2 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/grep -i 'out of memory' /var/log/syslog

The warning when you added the memory limit is harmless, it is just letting you know there's no swap file.

The flapping I'm referring to are these entries, it's likely a container starting and stopping repeatedly:

Jul 27 11:01:23 UNRAID kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth55e566d: link becomes ready

Jul 27 11:01:23 UNRAID kernel: br-33e69eebc9ce: port 8(veth55e566d) entered blocking state

Jul 27 11:01:23 UNRAID kernel: br-33e69eebc9ce: port 8(veth55e566d) entered forwarding state

Jul 27 11:01:23 UNRAID Docker Auto Update: Restarting nextcloud-aio-redis

Jul 27 11:01:23 UNRAID kernel: br-33e69eebc9ce: port 9(veth82c5f3b) entered blocking state

Jul 27 11:01:23 UNRAID kernel: br-33e69eebc9ce: port 9(veth82c5f3b) entered disabled state

Jul 27 11:01:23 UNRAID kernel: device veth82c5f3b entered promiscuous mode

Jul 27 11:01:23 UNRAID kernel: br-33e69eebc9ce: port 9(veth82c5f3b) entered blocking state

Jul 27 11:01:23 UNRAID kernel: br-33e69eebc9ce: port 9(veth82c5f3b) entered forwarding state

Jul 27 11:01:24 UNRAID kernel: eth0: renamed from vethf207f46

Jul 27 11:01:24 UNRAID kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth82c5f3b: link becomes ready

Gotcha. Thanks for your help!

I think I remember doing that search after nginx stopped.