[Bug]: CPU usage reaches over 100% before freezing host computer #408
-
Controller Versionv5.13 Describe the BugAfter starting docker container, the below process begins to eat up CPU until it eventually passes 100% and locking up the entire computer. The computer ends up requiring power be cut manually to restart it.
During this time, the controller is never available on
I've been trying things like limiting the docker container's memory or cpu w/ Expected BehaviorDocker container should start omada controller successfully, eventually making the web app accessible at Any help getting this to run on my Raspberry Pi 3B+ would be very much appreciated as I'd much prefer this to buying the hardware controller or running the software controller on my full-size desktop that I use for a lot of other things and restart regularly. Steps to Reproduce
How You're Launching the Container
Container Logs
MongoDB Logs
Additional ContextIn case any of this is relevant: Host Ubuntu version output:
Docker version output:
And pc arch output:
Some more stuff I've seen you ask for in other issues:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Honestly, your system is may be swapping like mad with You can check with another terminal open, regularly checking Just to make sure you're definitely doing this, I would try a few different CMDs to override the default amount of memory: 512m: Or even 256m: The biggest issue I would think it going on is that MongoDB is gonna eat up a good bit of RAM too. |
Beta Was this translation helpful? Give feedback.
Honestly, your system is may be swapping like mad with
Total Memory: 841.3MiB
. That's not a lot of RAM at all in order to run the controller. It may also be possible that your sd card is really slow for read/writes, assuming it is using an sd card. The log messages from MongoDB are concerning.You can check with another terminal open, regularly checking
free -m
anddocker stats
when the container is launched to see what is happening with your system's resources. Looking athtop
is good too, assuming you know what you're looking at of course. Not always intuitive if you haven't used it previously.Just to make sure you're definitely doing this, I would try a few different CMDs to override …