# בעיה בבנייה מחדש בגלל כיבוי איטי של מסד הנתונים

**URL:** <https://meta.discourse.org/t/problem-rebuilding-because-of-slow-database-shutdown/262366>\
**Category:** Self-hosting\
**Created:** [19 באפריל,‏ 2023,‏ 6:36pm UTC](https://meta.discourse.org/t/problem-rebuilding-because-of-slow-database-shutdown/262366 "2023-04-19T18:36:27Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Wingtip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/wingtip/32/102039_2.png) [@Wingtip](https://meta.discourse.org/u/Wingtip)\
**Post date:** [19 באפריל,‏ 2023,‏ 6:36pm UTC](https://meta.discourse.org/t/problem-rebuilding-because-of-slow-database-shutdown/262366/1 "2023-04-19T18:36:27Z")

</div>

This recommended upgrade failed and didn’t get my forum back up after breaking. I’m running discourse-doctor now to try to fix it, and if that fails too, I took a VM snapshot.

Output:

```plaintext
2023-04-19 18:28:31.298 UTC [42] LOG: received fast shutdown request
2023-04-19 18:28:33.651 UTC [65] LOG: shutting down
2023-04-19 18:28:33.974 UTC [42] LOG: database system is shut down

FAILED
--------------------
Pups::ExecError: su postgres -c 'psql discourse -c "alter schema public owner to discourse;"' failed with return #<Process::Status: pid 59 exit 2>
Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec failed with the params "su postgres -c 'psql $db_name -c \"alter schema public owner to $db_user;\"'"
bootstrap failed with exit code 2
**FAILED TO BOOTSTRAP** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
c13e1ba313de8fc84f6e2fb0f88197a908803c39791283effb8c82f55b56b6dc
Command exited with non-zero status 1
1.85user 1.84system 3:21.56elapsed 1%CPU (0avgtext+0avgdata 36996maxresident)k
197608inputs+368outputs (1133major+96509minor)pagefaults 0swaps

```

---

_[View the full topic](https://meta.discourse.org/t/problem-rebuilding-because-of-slow-database-shutdown/262366)._
