SOLVED "Platform data" and "Other" disk usage
yusf last edited by girish
With the new disk usage visualization I can see that "Platform data" takes up a whopping 19GB on a Cloudron instance of mine. "Other" is also hogging. Is that reasonable?
This does look a bit excessive. Can you dig a bit further there and see which part of platform data consumes much?
You can see that with
du -sh /home/yellowtent/platformdata/*via SSH.
yusf last edited by
I got helped out by gramakri. It was some 19GB log file taking up space. I will know where to look next time.
Are there other optimizations possible? For instance, outdated docker images?
@yusf: Can you post your solution? Where is the log file located and what did you do with it (just delete it)? What about the "Other"?
d19dotca last edited by
I just noticed mine at 10.24 GB for "Other". What is that and how do we clear it up (if it's even safe to do so)?
Side note: Would be great if the feature graph would also do the math to show how much remaining space exists so we don't have to do the math ourselves. I think I'll file that feature request separately later on.
@d19dotca Please check the size of
/home/yellowtent/platformdata/logs. We have a logrotate issue which is not cleaning up logs properly. You can delete some of the old files there safely.
I have the same problem.
Backups i can understand but Docker folder is kind of big.
du -sh /home/yellowtent/platformdata/*
@Warez Did you use
du -hcsto get docker storage size? Because the du tool does not work correctly with the overlayfs that docker uses. Instead use
docker system dfoutput.
TYPE TOTAL ACTIVE SIZE RECLAIMABLE
Images 10 9 2.591GB 1.33GB (51%)
Containers 10 9 0B 0B
Local Volumes 22 18 21.79MB 31.76kB (0%)
Build Cache 0 0 0B 0B
@Warez The 2.5GB there seems OK. Our docker app images are not disk usage optimized.
I understand, but why does cloudron report Other 82.82 GB?
"Other" might not be the best term in hindsight. Basically it is just the sum of everything else on the system. For example the Linux system/distro data itself, as well as data which is otherwise placed outside of Cloudron known folders, if any.
If anyone has a better term for that, to convey this information, I am happy to adjust it, if we find a good one.
@nebulon what about just "System"
I have another question regardiing this. The following is the output of docker system df.
$ docker system df TYPE TOTAL ACTIVE SIZE RECLAIMABLE Images 34 16 9.857GB 6.508GB (66%) Containers 21 18 0B 0B Local Volumes 160 36 5.274GB 3.964GB (75%) Build Cache 0 0 0B 0B
As you can see, docker claims that a lot of storage is reclaimable.
Is it safe to run
docker volume pruneand
docker image prune?
The prune commands should be safe to run. Unless there is some Cloudron bug, it shouldn't remove anything.
@girish thank you.
That worked for
docker volume prune. The other command (
docker image prune) did not actually clean anything up though, but the output of
docker system dfstays with 66% reclaimable.
Any further ideas?
yusf last edited by
@yusf Do you know which log is taking up space? Maybe we miss a logrotation rule somewhere. You can find this by
du -hcs /home/yellowtent/platformdata/logs/*
d19dotca last edited by d19dotca
@girish For what it's worth, I ran that command and found the total size was 872 MB. Is that expected? It seems like a lot to me to be nearly a GB in size just for text files. I'd expect that to be more around the 200 MB mark or so, but I'm not sure of the logrotate rules and how much gets logged generally nor how quickly.
I noticed one of the larger log files was around 47 MB on its own, and it looks to be from my Radicale app. It seems to be logging in DEBUG mode, which I presume is not intended? I'm guessing for production systems we'd like to keep logs in a normal INFO mode, right?
mm, OK. I looked into your own installation - https://paste.cloudron.io/eqixarerox.css (~800MB)
logrotate configs are in
Some apps like
2f004a04-e256-426b-9485-e06a31adc2ddwere missing configs. This is because when we added the new configs many releases ago, we didn't go back and re-generate it for all the apps. To fix this, simply enable and disable recovery mode and then the logrotate config will be generated.
turn, the logrotate was not added when we added it in the previous release. I have fixed this now for next release.
For all apps/services, we keep up to 2 logs of 10M. This is why most of them are < 20M. So, this is mostly working as expected.
For the rest, I see that log files are > 20M. I wonder why... investigating.
Found out why. If a log file is > 20M at rotation time, then it's never truncated. Looks like this is just how logrotate works.
necrevistonnezr last edited by
For me it adds up to 699 MB
Is there a way to clean up those logs in between?
@necrevistonnezr If you go into
/home/yellowtent/platformdata/logrotate, do you see
c5c137fa-0221-4d42-b418-10e544cebad1there? If not, go those apps (you can figure this out either by looking at the logs a bit or in the dashboard's URL) and start recovery mode and end recovery mode. This will generate the logrotate configs for them.
Once, the configs are in place, future logs will get rotated. But this does not help the current logs. You can just truncate them like:
truncate -s0 /home/yellowtent/platformdata/logs/07e4e251-ed90-42ca-9ba3-e015b108f1e6/app.log
necrevistonnezr last edited by
@girish Thanks, worked!