# No timeout for backups (stuck since September)

**URL:** <https://meta.discourse.org/t/no-timeout-for-backups-stuck-since-september/139641>\
**Category:** Bug\
**Created:** [January 24, 2020, 4:00pm UTC](https://meta.discourse.org/t/no-timeout-for-backups-stuck-since-september/139641 "2020-01-24T16:00:04Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![benjaoming](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/benjaoming/32/161986_2.png) [@benjaoming](https://meta.discourse.org/u/benjaoming)\
**Post date:** [January 27, 2020, 4:17pm UTC](https://meta.discourse.org/t/no-timeout-for-backups-stuck-since-september/139641/6 "2020-01-27T16:17:11Z")

</div>

Thanks for reading and responding! I noticed the issue while inspecting an old server, which has now been replaced. I still have access to the old instance.

- It happened on 1.8
- The only emails sent were `new_version` emails. No password resets, no notifications.
- Logs are often written to and flushed in different threads/processes, so I’m not sure if that can explain the stray `pg_dump` message.. but it’s certainly very suspicious.

I think the actual issue would perhaps also be that there’s no sanity checks when sending out a pile of emails in a queue. What if a password reminder is 3 months old? Should we assume that system time has changed or indeed that emails have failed to send for a considerable duration?

Our new server is now running the latest version of Discourse, but it would of course be a shame if unattended backups once again get stuck. [https://community.learningequality.org/](https://community.learningequality.org/)

---

_[View the full topic](https://meta.discourse.org/t/no-timeout-for-backups-stuck-since-september/139641)._
