# Discourse update doesn't wait for Postgress DB to shut down

**URL:** <https://meta.discourse.org/t/discourse-update-doesnt-wait-for-postgress-db-to-shut-down/212961>\
**Category:** Self-hosting\
**Created:** [December 23, 2021, 1:35pm UTC](https://meta.discourse.org/t/discourse-update-doesnt-wait-for-postgress-db-to-shut-down/212961 "2021-12-23T13:35:24Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![michaeld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaeld/32/1594_2.png) [@michaeld](https://meta.discourse.org/u/michaeld)\
**Post date:** [December 23, 2021, 5:50pm UTC](https://meta.discourse.org/t/discourse-update-doesnt-wait-for-postgress-db-to-shut-down/212961/2 "2021-12-23T17:50:21Z")

</div>

> [@kinetiksoft](#):
>
> ```plaintext
> 2021-12-22 12:04:08.808 UTC [53] LOG: database system shutdown was interrupted; last known up at 2021-12-22 12:02:56 UTC
> 2021-12-22 12:04:09.928 UTC [53] LOG: database system was not properly shut down; automatic recovery in progress
> 2021-12-22 12:04:09.972 UTC [53] LOG: redo starts at 83/B07EB758
> 2021-12-22 12:04:10.123 UTC [53] LOG: invalid record length at 83/B12EDED8: wanted 24, got 0
> 2021-12-22 12:04:10.123 UTC [53] LOG: redo done at 83/B12EDEA0
> 
> ```

It’s not shutting down, it’s not starting up properly because the redo log is damaged. If you have a backup you should consider recovering it on a blank instance.

---

_[View the full topic](https://meta.discourse.org/t/discourse-update-doesnt-wait-for-postgress-db-to-shut-down/212961)._