Fix common problems gave me an out of memory error warning, which directed me to a recommendation to make a post here and include diagnostics. This is the first time I have ever received the warning.

My RAM usage is sitting at 18% of total available, and I have never seen it near 100% (I have 64 gb which is generally well above my needs).

I have not experienced anything in particular to be an issue, although I did recently have to re-build my docker image. That was following an unclean shutdown, which I could not find any way to avoid. SSH, direct access and the power button were unresponsive to start a clean shutdown. I have had that happen once before, although I have no reason to think this is related. Since this rebuild, I have noticed that the docker window is frequently slow to load, but is working fine other than that issue.

tower-diagnostics-20251003-1449.zip

12 hours ago, QMoney said:

although I have no reason to think this is related

Probably not related

Go to the docker tab and toggle the advanced view and see which container has this ID (or close to it) 7d3934da0c4f - it may be nginx proxy manager as another user recently had the same node process running way going OOM and being killed. I can't offer any advice as to why it's doing that, I have been running it for years and have never seen it do that, best I can advise is to re-install it.

You will need to restart the sever to clear the log

You should also try to figure out what's going on with these, it's flooding your log

Oct  3 14:37:35 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is reachable again
Oct  3 14:47:46 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is unreachable
Oct  3 14:47:46 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is reachable again
Oct  3 14:47:55 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is unreachable
Oct  3 14:48:40 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is reachable again
Oct  3 14:48:48 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is unreachable
Oct  3 14:49:22 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is reachable again
Oct  3 14:49:30 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is unreachable
Oct  3 14:49:30 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is reachable agai

On 10/4/2025 at 3:23 AM, Michael_P said:

Go to the docker tab and toggle the advanced view and see which container has this ID (or close to it) 7d3934da0c4f - it may be nginx proxy manager as another user recently had the same node process running way going OOM and being killed. I can't offer any advice as to why it's doing that, I have been running it for years and have never seen it do that, best I can advise is to re-install it.

Sure enough, that is NGINX Proxy Manager... I've been running it for quite a while and never had the issue before. What's odd, is that I've never set a limit on it's memory, but I am seeing that it is my only container that is allocated less than the max 62.58 GB of ram. It looks like it only has 1 GB to work with, which I can now see probably comes from the extra parameters that must have been included in the template from the app store of "--memory=1G --no-healthcheck". These appear to be pretty standard parameters, as seen in this post.

Thanks for the guidance, you're a gem! I'm thinking I should mark this solved since we know what container it probably is, and it's possible that it is known to potentially go on a run with memory hence the limiting parameter. If it happens again, I'll go to the container support forum or github. Let me know if you have any other suggestions.

I did a restart after I saved the diagnostics, haven't had an issue with it since, but I will keep an eye on this container and poke around forums when I can.

On 10/4/2025 at 3:23 AM, Michael_P said:

You should also try to figure out what's going on with these, it's flooding your log

Oct  3 14:37:35 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is reachable again
Oct  3 14:47:46 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is unreachable
Oct  3 14:47:46 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is reachable again
Oct  3 14:47:55 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is unreachable
Oct  3 14:48:40 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is reachable again
Oct  3 14:48:48 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is unreachable
Oct  3 14:49:22 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is reachable again
Oct  3 14:49:30 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is unreachable
Oct  3 14:49:30 Tower dhcpcd[1976]: br0: fe80::be24:11ff:fe4c:4bc3 is reachable agai

Thanks for catching that! I do need to figure it out. I probably could just disable IPV6... but I think I need to fix the subnet for ipv6. It's hard to find times to shut down docker and fiddle with this stuff. I was messing around for a while working out some issues with the IPV4 aspects of vlans, and want to challenge myself to get better with ipv6.

I very courteous bow and a tip 'o the cap to you! Thanks!