My forum is 1 month old, ~15000 posts… I tried checking it tonight and received a 502 error. I then reloaded my Droplet and tried a ./launcher rebuild and was met with a "785ef3cb0f4bbe86b21afde2620a966a63e03427e89484b0946a94d1bb34-init: no space left on device. See '/usr/bin/docker run --help'. Your Docker installation is not working correctly" So I did a df -h and saw that my disk was completely full: Filesystem Size Used Avail Use% Mounted on udev 981M 0 981M 0% /dev tmpfs 201M 3.1M 197M 2% /run /dev/vda1 39G 39G 0 100% / tmpfs 1001M 0 1001M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 1001M 0 1001M 0% /sys/fs/cgroup tmpfs 201M 0 201M 0% /run/user/0 How could this have happened? I tried apt-get autoclean and apt-get autoremove which didn’t help. Also did ./launcher clean and that didn’t help. Also tried sudo du -xh -d 1 My disk space is still 39GB/39GB :frowning:

I did try that. I get the same out of space message when trying to cleanup: ./launcher: line 96: cannot create temp file for here-document: No space left on device ./launcher: line 97: cannot create temp file for here-document: No space left on device ./launcher: line 96: cannot create temp file for here-document: No space left on device ./launcher: line 97: cannot create temp file for here-document: No space left on device ./launcher: line 96: cannot create temp file for here-document: No space left on device ./launcher: line 97: cannot create temp file for here-document: No space left on device ./launcher: line 96: cannot create temp file for here-document: No space left on device ./launcher: line 97: cannot create temp file for here-document: No space left on device /usr/bin/docker: Error response from daemon: mkdir /var/lib/docker/aufs/mnt/6dfedd25fd4d18e682780fc168b2f42ad42b1fee8a4f21b7728f8b4ecf36e51b-init: no space left on device. See '/usr/bin/docker run --help'. Your Docker installation is not working correctly This doesn’t seem normal for a forum my size to take up 39GB?

Two things come to mind: If your instance was populated with a restore, or imported from another platform you may be carrying the restore schema around: https://meta.discourse.org/t/disk-space-usage-by-postgres/61137 backups left on disk have filled your space: Check /var/discourse/shared/standalone/backups/default The backups are .tar.gz files Look at the date AND size of the backups before you start deleting.

My instance was a fresh install. You read my mind on the automatic backups. I was trying to figure out what I could remove to clear enough space for the ./launcher cleanup to work. So I went into /var/discourse/shared/standalone/backups/default and deleted a few of the old backups which cleared about 150mb of space. I then was able to run ./launcher cleanup and that netted me back 16GB of space. I still have 24GB used up which seems like quite a lot for a forum my size. Now my other problem is, I did a reboot on my droplet and ever since I did that, the initial 502 Gateway issue has turned into a Failed to open page issue. I still can’t get access to my Discourse, even after do a ./launcher rebuild

@Ericsworld upload your backups to Amazon S3 – this way you save space on your discourse instance

[image] Ericsworld: Now my other problem is, I did a reboot on my droplet and ever since I did that, the initial 502 Gateway issue has turned into a Failed to open page issue. I still can’t get access to my Discourse, even after do a ./launcher rebuild What’s in the logs? Share those :wink:

Hmn… Now that you’ve enough headroom, what about apt-get update and apt-get upgrade? Once your droplet went into tilt mode not only the updates to discourse will have failed, but also any to the underlying OS. Can you see /logs and /sidekiq? What about /safemode? Sorry if my answers are a bit generic, I’m still on my first coffee.

Oops my mistake, I did the rebuild again and it went through correctly. Site is back up :slight_smile: I just did another df -h and it is up to a 83% usage after rebuilding the app. root@discourse-2gb-sfo1-01:/# df -h Filesystem Size Used Avail Use% Mounted on udev 981M 0 981M 0% /dev tmpfs 201M 8.2M 192M 5% /run /dev/vda1 39G 32G 6.9G 83% / tmpfs 1001M 1.2M 999M 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 1001M 0 1001M 0% /sys/fs/cgroup tmpfs 201M 0 201M 0% /run/user/0 none 39G 32G 6.9G 83% /var/lib/docker/aufs/mnt/a6afa8c2711ae69fa62074c1a807463fae0a91b1b5c48cf34244df5a652cd90f shm 64M 4.0K 64M 1% /var/lib/docker/containers/b75645ecd758ef2627d6d6d9e117757a97928851a2706a091492c3789ba65e0c/shm So I fear this is not going to last… what is taking up all this space??

[image] Ericsworld: So I fear this is not going to last… what is taking up all this space?? How large are your backups? What about uploads?

Also – I’d recommend getting more disk space.

A backup of my discourse is 5.9GB… Where can I check the upload usage? I don’t think it’s normal for a forum my size to be using up 32GB like this… or I guess it is normal. DigitalOcean’s Volume Block Storage isn’t available in my server’s region, I will need to look into that to add in more space.

Completely Out of Disk Space

Product Support Self-hosting

robbyoconnor (Robby O'Connor) June 4, 2017, 2:06am 20

Or toss the backups on Amazon S3…including uploads in backups is useful.

Topic		Replies	Views
My website is always down Self-hosting	46	2909	April 22, 2022
Why the forums takes full of total 20Gb of disk? Self-hosting	6	1313	March 19, 2016
Disc too full without much data in the forum Self-hosting	8	650	January 21, 2021
Unable to rebuild discourse due to no space left on device Self-hosting	32	3778	November 19, 2022
Discourse upgrade fails due to insufficient disk space on 25G droplet Self-hosting server-resources	38	2350	March 30, 2022

Completely Out of Disk Space

Related topics