# Failed to bootstrap - pups

**URL:** https://meta.discourse.org/t/failed-to-bootstrap-pups/282956
**Category:** Self-hosting
**Created:** [October 21, 2023, 1:50am UTC](https://meta.discourse.org/t/failed-to-bootstrap-pups/282956 "2023-10-21T01:50:13Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Senthil](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/senthil/32/116238_2.png) [@Senthil](https://meta.discourse.org/u/Senthil)
#### Post date: [October 21, 2023, 1:50am UTC](https://meta.discourse.org/t/failed-to-bootstrap-pups/282956/1 "2023-10-21T01:50:13Z")

</div>

- I am running into a upgrade issue after a recent update.

- The app suddenly stopped for me with the “oops” message.

- And then as I am trying to trying to the update (./launcher rebuild app), I am running into this.

- I have disabled all plugins too.

Any suggestions on how to bring my app back up?

```plaintext

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 749 exit 1>
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 {"cd"=>"$home", "hook"=>"db_migrate", "cmd"=>["su discourse -c 'bundle exec rake db:migrate'"]}
bootstrap failed with exit code 1
**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.
481a982e1362643c5caed63c5d9fdc1312e051782b7cb43d151c39421ff8adcd

```

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [October 21, 2023, 3:15am UTC](https://meta.discourse.org/t/failed-to-bootstrap-pups/282956/2 "2023-10-21T03:15:43Z")

</div>

You need to

> [@Senthil](#):
>
> please scroll up and look for earlier error messages, there may be more than one.`

---

<div class="post-metadata">

### Author: ![Senthil](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/senthil/32/116238_2.png) [@Senthil](https://meta.discourse.org/u/Senthil)
#### Post date: [October 21, 2023, 11:20am UTC](https://meta.discourse.org/t/failed-to-bootstrap-pups/282956/3 "2023-10-21T11:20:57Z")

</div>

I commented out all the plugins except the docker manager and my site was up. I need to now enable one plugin at a time and see where the problem was.

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [October 21, 2023, 11:34am UTC](https://meta.discourse.org/t/failed-to-bootstrap-pups/282956/4 "2023-10-21T11:34:17Z")

</div>

There were likely more detailed errors in the output above what you posted that may have helped you narrow it down. If you have any third-party plugins they would be a good place to start. If you can list them here we may be able to recognise any known issues?

---

<div class="post-metadata">

### Author: ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [October 21, 2023, 12:15pm UTC](https://meta.discourse.org/t/failed-to-bootstrap-pups/282956/5 "2023-10-21T12:15:31Z")

</div>

(It’s very common to have to ask people to scroll up and post more of their logs: could that **please scroll up** message perhaps have more words? Posting the last 200 lines of output would (I guess) cover most cases.)

---

<div class="post-metadata">

### Author: ![kuaza](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kuaza/32/264151_2.png) [@kuaza](https://meta.discourse.org/u/kuaza)
#### Post date: [October 21, 2023, 1:10pm UTC](https://meta.discourse.org/t/failed-to-bootstrap-pups/282956/6 "2023-10-21T13:10:33Z")

</div>

I was also experiencing errors during the update. It’s about plugins. For example, it was the chatbot plugin that caused the error for me. You can fix it by finding which plugin is causing the problem.
