Is this meant to happen when I run the rebuild command?

@pfaffman Sorry if this in the wrong place but can I just add that after the rebuild I tried a backup from the admin section, it failed but I got a solid error log and a notification:

[2018-02-05 23:05:17] Marking backup as running...
[2018-02-05 23:05:17] Making sure '/var/www/discourse/tmp/backups/default/2018-02-05-230517' exists...
[2018-02-05 23:05:17] Making sure '/var/www/discourse/public/backups/default' exists...
[2018-02-05 23:05:17] Pausing sidekiq...
[2018-02-05 23:05:17] Waiting for sidekiq to finish running jobs...
[2018-02-05 23:05:17] Backup process was cancelled!
[2018-02-05 23:05:17] Notifying 'vapingcommunity' of the end of the backup...
[2018-02-05 23:05:23] Removing old backups...
[2018-02-05 23:05:23] Cleaning stuff up...
[2018-02-05 23:05:23] Removing '.tar' leftovers...
[2018-02-05 23:05:23] Unpausing sidekiq...
[2018-02-05 23:05:23] Marking backup as finished...
[2018-02-05 23:05:23] Finished!

So can we assume that a rebuild somewhat fixed the backup process or changed it in some way?

These don’t exist in my screenshot?

Making sure '/var/www/discourse/tmp/backups/default/2018-02-05-230517' exists...
Making sure '/var/www/discourse/public/backups/default' exists...

Edit: Backup in the admin section worked!! :smiley: