Unable to rebuild discourse due to no space left on device

installation
24

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

2 Likes
25

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?

4 Likes
26

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!

27

There is a topic about that. I would likely move backups to Spaces first.

What about this

   du -hs /var/discourse/shared/*
28

I have backups set up on DO Spaces. I thought the backup failed due to not having enough space locally?

29

Oops

 du -hs /var/discourse/shared/standalone/*

Oh. Yes, local storage is the problem, but an easy way to solve it is moving backups, but you did that already…

But maybe you can do a

 ./launcher cleanup

And get back space from docker

30

This is the output:

root@forum:~# du -hs /var/discourse/shared/standalone/*
124G    /var/discourse/shared/standalone/backups
21M     /var/discourse/shared/standalone/letsencrypt
2.9G    /var/discourse/shared/standalone/log
4.0K    /var/discourse/shared/standalone/postgres_backup
74G     /var/discourse/shared/standalone/postgres_data
264K    /var/discourse/shared/standalone/postgres_run
5.1G    /var/discourse/shared/standalone/redis_data
44K     /var/discourse/shared/standalone/ssl
28K     /var/discourse/shared/standalone/state
16K     /var/discourse/shared/standalone/tmp
9.2G    /var/discourse/shared/standalone/uploads

I ran ./launcher cleanup two days ago and it didn’t solve the backup fail problem. :confused:

31

You have too much storage being consumed by your backups. You’ll need to rethink your backup strategy and possibly move backups to an external storage like S3.

1 Like
32

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.

2 Likes
33

I believe it’s the latter because I do see my backup files on my DO Spaces. What is the best practice to delete the backups? Can I remove the content with the following command?

rm -r /var/discourse/shared/standalone/backups

Thank you!

1 Like
34

That should do the trick!

1 Like
35

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

1 Like
36

Hooray! With 126Gb free, you should be good for a while!

1 Like
37

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.