Hi all

I was just doing a little housekeeping on my unRAID server, and was checking out the Fix Common Problems plugin and there was a message saying that the server was running out of memory and to post here and share my Diagnostic file.

The server has been running great for some time. Last night though I was tidying up my desk and accidentally I cut power to the server, so major unclean shutdown. Then my VM's wouldn't start automatically and when I did start them myself I wasn't able to access the unRAID GUI and had to do another unclean shutdown. Eventually all was good, though I noticed that my Windows VM initially was very laggy, but it's all good now. I also had an issue with the Docker service and had to delete the Docker file and then reinstall all the apps, but that went smoothly. So the only issue I seen to have now is this memory issue that unRAID is reporting. I considered shutting down the server to reboot but I don't know if this will clear this message.

Thanks in advance for your help!

tower-diagnostics-20250709-1131.zip

7 hours ago, HomerJ said:

Hi all

I was just doing a little housekeeping on my unRAID server, and was checking out the Fix Common Problems plugin and there was a message saying that the server was running out of memory and to post here and share my Diagnostic file.

The server has been running great for some time. Last night though I was tidying up my desk and accidentally I cut power to the server, so major unclean shutdown. Then my VM's wouldn't start automatically and when I did start them myself I wasn't able to access the unRAID GUI and had to do another unclean shutdown. Eventually all was good, though I noticed that my Windows VM initially was very laggy, but it's all good now. I also had an issue with the Docker service and had to delete the Docker file and then reinstall all the apps, but that went smoothly. So the only issue I seen to have now is this memory issue that unRAID is reporting. I considered shutting down the server to reboot but I don't know if this will clear this message.

Thanks in advance for your help!

tower-diagnostics-20250709-1131.zip

Looks like it ran OOM twice yesterday around 1920-1930, and killed the docker service both times. Doesn't appear to be any particular container, and is likely just trying to do too much at once. Check your container configs to make sure anything that you have caching to RAM isn't going to exhaust the host, and consider limiting the RAM available to the container. Reboot to clear the log so FCP stops warning you.