[image] I get the aforementioned error while attempting to do an operation. I have no idea as to why this is happening.

[image] littleviolette: I have backups set up on DO Spaces Either you don’t have backups on spaces or you didn’t delete the local backups when you switched to it. You can delete those backups and be in good shape.

Kind of unavoidable I think we bumped base image 2 times in the last few months. Not much we can do. Looks like the cleanup on your server shaved off 2 base images.

anon43908006: Whats the easy way to rebuild a discourse server and reinstall letsencrypt please? @anon43908006, there is a guide at: [image] Change the domain name or rename your Discourse Self-Hosting bookmark This guide explains how-to change the domain name of your Discourse site, and includes information about setting up DNS changes, editing configuration files, updating site settings, and correcting social logins and post content to reflect your new domain name. warning This guide is for self-hosted Discourse instances that were installed using our installation guide on GitHub. If you are hosted by Discourse, please see Configure your domain name for hosted Discourse for specific … It goes over many considerations for changing your domain, check it out. :slight_smile:

[image] codinghorror: is this something we should be concerned about? :thinking: [image] sam: Not much we can do. To clarify, is there not much to do about the overall size of the upgrades increasing, or not much to do about the recent spike in bumping base image activity (which will not affect as much in the future)? I’v been surprised, I’ve got all these tiny Discourses with very few users, and kept running into this issue lately. No uploads or anything. I was wondering if we are approaching a point where the cloud install will recommend the next size up on drive space (which is 2GB RAM/1vCPU/50GB SSD). :thinking:

I asked @falco about this in chat and he said lately we’ve had a lot of base image changes due to dependencies being updated, so there’s been a higher than usual amount of disk space in upgrades in the last ~6 months.

Sorry to hear you’ve run into trouble changing your domain name, @anon43908006. Because this is #support, I encourage you to create a new topic that explains your exact case: it may be that your situation requires more discussion than what’s happening in this topic, which is more of a general pattern we’ve been noticing. If you’d like, you can mention me (@maiki) and I’d be happy to discuss what’s going on with your site. :slight_smile:

I get the same No space left on device error when I try to backup my Discourse: [2022-11-15 08:23:38] EXCEPTION: /var/www/discourse/lib/discourse.rb:131:in `exec': Failed to gzip archive. gzip: /var/www/discourse/public/backups/default/forum-leasehackr-2022-11-15-080439-v20221110175456.tar.gz: No space left on device My backup and image uploads are set up on DigitalOcean’s Spaces and have been working fine for a few years until recent months. Here are what I have tried so far: I cleared all hidden multipart uploads on my DO Space. There should be more than 100GiB of storage available on my DO Space. I tried rebuilding and cleaning up using the following commands: cd /var/discourse apt-get update apt-get upgrade apt-get autoclean apt-get autoremove ./launcher rebuild app ./launcher cleanup Anyone knows why my backups keep failing still? Thank you!

Check to see if you have leftover backups here and delete them: /var/discourse/shared/standalone/backups/default

[image] littleviolette: There should be more than 100GiB of storage available on my DO Space. This message is about your local disk. To create a backup you need to have almost twice the size of your database+uploads available to create the backup that gets uploaded to spaces. What do these show you? df -h du -hs /var/discourse/shared/* du -hs /var/discourse/shared/standalone show you?

This is what the commands show: root@forum:~# df -h Filesystem Size Used Avail Use% Mounted on udev 7.9G 0 7.9G 0% /dev tmpfs 1.6G 169M 1.5G 11% /run /dev/disk/by-label/DOROOT 315G 277G 22G 93% / tmpfs 7.9G 4.9M 7.9G 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup cgmfs 100K 0 100K 0% /run/cgmanager/fs none 315G 277G 22G 93% /var/lib/docker/aufs/mnt/990236bd36313269b6683947dc21241f4387b2671676e8fdf68de05c0fb3e0f4 shm 512M 22M 491M 5% /var/lib/docker/containers/4684612f16f4f31589ae8075145bcde0e6e9576a22eaef3952e9d47986999b91/shm tmpfs 1.6G 0 1.6G 0% /run/user/0 root@forum:~# du -hs /var/discourse/shared/* 215G /var/discourse/shared/standalone root@forum:~# du -hs /var/discourse/shared/standalone 215G /var/discourse/shared/standalone If it’s a local storage issue, can I simply add block storage (Volumes) to the DigitcalOcean Droplet? Thank you!

[image] littleviolette: I simply add block storage (Volumes) to the DigitcalOcean Droplet There is a topic about that. I would likely move backups to Spaces first. What about this du -hs /var/discourse/shared/*

Unable to rebuild discourse due to no space left on device

Product Support Self-hosting

littleviolette November 19, 2022, 10:25pm 35

That was indeed the cause. Just cleared out the local backup folder and backup works again. Thank you for your help!

Topic		Replies	Views
My website is always down Self-hosting	46	2909	April 22, 2022
I got an error after updating my forked install Self-hosting unsupported-install	35	2344	November 13, 2018
Stuck in a loop of freeing up space and filling it up again when rebuilding Self-hosting server-resources	30	4344	March 20, 2019
Errno::ENOSPC: No space left on device Product Support docker	16	14261	June 1, 2017
Discourse upgrade fails due to insufficient disk space on 25G droplet Self-hosting server-resources	38	2349	March 30, 2022

Unable to rebuild discourse due to no space left on device

Related topics