Cloudron Forum

@nebulon about 15-20 every second. When it stops there is a line box:apphealthmonitor app health: 28 alive / 4 dead. Nothing about accessing any sites though.

Hello @girish, Just lost a lot of time on a bug related to storage and I then discover that what shows in the cloudron UI was in fact Binary, can be updated the label to the correct one with the "i" in-between letters, so that it's clear what unit of measurement is been used? KiB kibibyte MiB mebibyte GiB gibibyte I know that is a stupid thing to complain but it can save some time on understanding what's happening sometimes.

@ruihildt Thanks for reporting. This is fixed in the coming release - https://git.cloudron.io/cloudron/box/-/blob/master/CHANGES#L1930

@ruihildt The issue in your case was different. There were so many apps that the query parameter limit was getting exceeded. This is fixed in next release. @necrevistonnezr this is most likely your issue as well!

Agree, the memory graphs are quite rudimentary at this point. We will rework them to be more useful and correct at some point.

Finally, one important bit: by default ext4 will reserve 5% of the disk for the root user. You can see this like so: root@strawberry:~# tune2fs -l /dev/sda1 | grep Reserved Reserved block count: 1562918 Reserved GDT blocks: 1024 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) 1562918 blocks * 4096 block size = ~6GB. You can reduce the percent to say 2 like this: tune2fs -m 2 /dev/sda1 Unless you have a big disk, I would leave it at 5%.

In the past, I think people have recommended integrating with netdata. I don't have experience with netdata but wanted to throw the idea out there. Other than that, current graphs is rendered using data collected by graphite/carbon.

This is fixed now, will be part of next release.

Interesting, this was simply missed I guess. I have added it now and it will be part of the next release. It will look like this then: [image: 1572952466019-screenshot_2019-11-05-cloudron.png]

Thanks, investigating this. I suspect the node module is unable to parse the output because of something in the output. I will keep you posted here.

I had to do the same thing before it was implemented to be changed under System -> Services in cloudron. By the way, the documentation is missing for it

@nebulon nevermind. It fixed itself. Weird.