Solved "socket hang up" when trying to display Memory Graph in Dashboard, no graphs displayed
-
Why would this happen? I have a VPS with 16 GB of RAM!
Is it because ssdnodes uses the XFS file system, and not ext4? Remember, the only way I could get Cloudron to install was to comment out the check for ext4 in the install script.
This is just one of a few issues that really bug me, and I wish I knew if it was something to do with XFS or something entirely different. I mean, 16 GB.... why would there be any problems running cloudron????
Thank you for looking into this.
image url) -
Take a look at docker stats graphite
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS c83fb2b97d77 graphite 0.09% 83.45MiB / 512MiB 16.30% 28.3MB / 821kB 0B / 0B 6I gave the container more RAM and the problem never occurred for me again. Standard setting is 75MiB with is not enough.
Note to @girish and @nebulon: It would be cool if we could change RAM for box, graphite and especially redis from the UI.
-
@subven said in "socket hang up" when trying to display Memory Graph in Dashboard, no graphs displayed:
docker stats graphite
Thank you for sharing this info. I see that my MEM USAGE was 72.6 / 75 MB limit, so that would indicate why it crashes. How do I increase the limit then?
A life lived in fear is a life half-lived
-
@scooke I did it with:
docker update --memory "256mb" --memory-swap "1g" graphitebut thats the very dirty way.
-
Whoops, didn't realize that graphite is actually not listed under services. Will add that for the next release.
-
This is now added for 3.6
-
@subven said in "socket hang up" when trying to display Memory Graph in Dashboard, no graphs displayed:
docker update --memory "256mb" --memory-swap "1g" graphite
There is no need to restart anything after that?
Thank you so much to the help! -
Yes, there is no need to restart after that.
