r/unRAID•
ggfools

unraid memory leak?

today I woke up and my unraid machine was completely unresponsive, i run a "homepage" docker instance and the last time it had updated the system had only 600MB ram free (I have 32GB ram in the machine and usually utilize only about 25% of that) i haven't added any new docker containers or anything in the last couple days just had the same ones running I've had for a couple weeks since I set up the system. anyway i did a hard reset since i couldn't access anything (maybe i should have plugged in a monitor and keyboard and tried to reset the system in command line, didn't really think about it) and now it's doing a parity check that will take about a day, how can I avoid this happening in the future? is there any best practice im missing?

Posted Jul 19, 2023, 3:18 PM UTC

110
SamSausages•

What version are you on?
Unraid/docker etc do use tempfs to put certain logs/info into memory, this is limited to 32MB (I think)
If that tempfs folder fills up, then it will lock up your system.

Best solution is to find out what is causing that, could be logs or healthchecks.

Here is a link on how to check that issue and some possible solutions:
https://forums.unraid.net/topic/133430-tmpfs-run-full/

1
ggfoolsOP•

thank you for the reply, i am on unraid 6.12.1, I will check out the steps in that link once I get back home

1
SamSausages•

There were some issues with docker filling up tempfs. It's probably best to upgrade to the latest version as the release notes mention some docker changes related to that issue.

1
ggfoolsOP•

ah ok I didn't know there was an update, suppose I should set it to check more then once a week, i will update as soon as the parity check is complete thank you for the help and suggestions

1
SamSausages•

Usually you're good staying on the same version. But 6.12 was a pretty big change for Unraid, so there are a few teething issues that they updated shortly after release.

1
TBT_TBT•

Then update to 6.12.3. a lot of bugs have been solved, as 6.12.0 had a lot of them.

1
rootd00d•

Look for a constant stream of repeated messages in your logs.

1
Schuhsohle•

Hey I had something nearly similar like you today. All my memory (32GB) ram was is use and all cores from the cpu were at 100%. Had htop running when this happened and I saw that avahi-daemon was the cause for this. Maybe it was the culprit also at your system

1
ggfoolsOP•

thanks for the heads up i will look into it

1