# Backup failed message doesn't mention specific error

**URL:** https://meta.discourse.org/t/backup-failed-message-doesnt-mention-specific-error/180314
**Category:** Bug
**Created:** [February 19, 2021, 7:04am UTC](https://meta.discourse.org/t/backup-failed-message-doesnt-mention-specific-error/180314 "2021-02-19T07:04:39Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Dannii](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dannii/32/129087_2.png) [@Dannii](https://meta.discourse.org/u/Dannii)
#### Post date: [February 19, 2021, 7:04am UTC](https://meta.discourse.org/t/backup-failed-message-doesnt-mention-specific-error/180314/1 "2021-02-19T07:04:40Z")

</div>

I got an admin message saying that the backup had failed, but it only had a stack trace:

> **Message**
>
> > The backup has failed.
> > 
> > Here’s the log:
> > 
> > ```plaintext
> > BackupRestore::BackupStore::StorageError
> > /var/www/discourse/lib/backup_restore/s3_backup_store.rb:84:in `rescue in unsorted_files'
> > /var/www/discourse/lib/backup_restore/s3_backup_store.rb:72:in `unsorted_files'
> > /var/www/discourse/lib/backup_restore/backup_store.rb:23:in `files'
> > /var/www/discourse/lib/backup_restore/backup_store.rb:28:in `latest_file'
> > /var/www/discourse/app/jobs/scheduled/schedule_backup.rb:12:in `execute'
> > /var/www/discourse/app/jobs/base.rb:232:in `block (2 levels) in perform'
> > /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rails_multisite-2.5.0/lib/rails_multisite/connection_management.rb:76:in `with_connection'
> > /var/www/discourse/app/jobs/base.rb:221:in `block in perform'
> > /var/www/discourse/app/jobs/base.rb:217:in `each'
> > /var/www/discourse/app/jobs/base.rb:217:in `perform'
> > /var/www/discourse/app/jobs/base.rb:279:in `perform'
> > /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/mini_scheduler-0.13.0/lib/mini_scheduler/manager.rb:93:in `process_queue'
> > /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/mini_scheduler-0.13.0/lib/mini_scheduler/manager.rb:37:in `block (2 levels) in initialize'
> > 
> > ```

Only when I went to the backups tab and clicked on the link to /admin/backups.json did I see the problem:

```plaintext
{"errors":["The AWS Access Key Id you provided does not exist in our records."]}

```

It would be good if this was included in the message as well.

(Also, I didn’t get any notifications for this message - it’s been sending one a day for ages! Any ideas why? I can’t see where I could’ve muted the admin group.)

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [February 22, 2021, 2:23am UTC](https://meta.discourse.org/t/backup-failed-message-doesnt-mention-specific-error/180314/2 "2021-02-22T02:23:42Z")

</div>

Any ideas if this can be improved @gerhard ?

---

<div class="post-metadata">

### Author: ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [March 2, 2021, 12:36pm UTC](https://meta.discourse.org/t/backup-failed-message-doesnt-mention-specific-error/180314/4 "2021-03-02T12:36:21Z")

</div>

Thanks for reporting those issues. I made a small adjustment to include the original error message.

[https://github.com/discourse/discourse/pull/12257](https://github.com/discourse/discourse/pull/12257)

> [@Dannii](#):
>
> Also, I didn’t get any notifications for this message - it’s been sending one a day for ages! Any ideas why?

This was caused by a bug.

[https://github.com/discourse/discourse/pull/12255](https://github.com/discourse/discourse/pull/12255)

---

<div class="post-metadata">

### Author: ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [March 2, 2021, 12:37pm UTC](https://meta.discourse.org/t/backup-failed-message-doesnt-mention-specific-error/180314/5 "2021-03-02T12:37:08Z")

</div>


