Cloudron Forum

Hello @miednr Always happy to help.

@jcalag said in uninstalled app not deleted: Errors were encountered while processing: nginx-core nginx-common It can't load the dashboard because nginx is not running. You can try some of the methods here - https://superuser.com/questions/1386209/how-to-solve-this-dependencies-apt-fix-broken-install

Hi @girish sorry for the delay. I think -D does not necessarily impact performance, my test after removing -D was much quicker but after adding it again it was just as quick. Seems like there's some kind of filesystem caching. Maybe at some point I could analyse the differences but I suspect changing this doesn't impact performance so much. The part that does impact performance a lot is the -x flag, but as far as I've seen, that will only prevent iteration on the remote (s3fs) filesystem if du is initiated on the parent dir, e.g. /mnt and not on the mount itself /mnt/s3fs. Would be a lifesaver if you could add this, but understandable if it cannot be done. If it cannot be done, a workaround to exclude certain volumes from disk usage calculation would be fine too. Or maybe you could add an option to the Disk Usage UI: Offer an option to include/exclude certain volumes before actually executing calculation

@webmaster we do offer direct support for businesses. We have a business plan exactly for businesses such as yours. If you are on a business plan, you can contact us at support@cloudron.io and we respond in a day.

@SansGuidon Yes, it's because of that syslog file. Thanks to your post, I was able to fix it. It seems like v8.3.2 (Ubuntu 24.04.3 LTS) is the only one with the error.

I fully support this. I know it’s not the same but you can build something like this in your .bashrc (and a cron script) so you have some info on the terminal. Mine looks like this after I ssh into my server: [image: 1757554341579-img_2366-resized.jpeg]

Closed due to inactivity

Thanks for reporting. This was bug in the container. I have reduced the verbosity to 0 in the mongod configuration for the next release. For the moment, you can simple delete or truncate the log files.

@perelin the docker usage is reported searately (the second line in your screenshot). It's around 20GB. This seems reasonable. The graphs numbers from du are not accurate when it comes to docker . You have to use docker system df . Looks like the space is being used somewhere else. Did you happen to use another backup location previously ? I guess the only way to find out is to run du on each folder starting from root

It looks like the problem is indeed gone with 8.1 Thank you!

As du is slow and resource hungry, maybe use an alternative? Diskus is a parallelized version: https://github.com/sharkdp/diskus, claims to be 5-10 times faster. Though not in the repos

Yes, that’s a build-in docker command that you can run in your ssh terminal

When I log in, the Empty Space has enlarged and back to the 16 Nov level. Weird though. Will keep an eye on it and report it if it rises again.

it's just a SSD so around 500 MB/s

@joseph said in Why does refreshing Disk Usage take so long?: but you can skip that backup disk from disk usage check . See the bottom of https://docs.cloudron.io/system/#disk-usage . Just add the path into /home/yellowtent/platformdata/diskusage/exclude I don't want to skip it! It was the one I wanted to check!

Maybe you have dangling images around, which are not deleted, can you see if docker image prune -a removes some?

The collabora app image is fairly large due to all the language support packages. So far we haven't found a way to make those dynamically selectable. Also it appears you have a lot of data for the system itself, possibly you have some old leftover backups in /var/backups which could be purged, if you have configured a proper backup storage?

@jpodner I had the same issue. Solved it by following the instruction on this page to extend my LVM space. https://packetpushers.net/ubuntu-extend-your-default-lvm-space/

Btw, I applied the changes of the system.js according to the changelog to solve this problem in my environment until the update is available. So at least for myself this Post could be set to "solved".