# Errors were encountered while processing: postgresql-contrib-9.5

**URL:** <https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670>\
**Category:** Self-hosting\
**Created:** [08.Ноябрь.2016 16:53:54 UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670 "2016-11-08T16:53:54Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![sphyden](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sphyden/32/121358_2.png) [@sphyden](https://meta.discourse.org/u/sphyden)\
**Post date:** [13.Декабрь.2016 16:52:15 UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/16 "2016-12-13T16:52:15Z")

</div>

I ended up getting Discourse over to my Cent 7 server, by pushing the current container to our registry, and copying the entire /var/docker directory over. I am able to get a functioning version of our Discourse working that way. I am still unable to update discourse due to the following error:

```
Pups::ExecError: /root/upgrade_postgres failed with return #<Process::Status: pid 40 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params "/root/upgrade_postgres"
e68c256f43b7101b5c7003b8db31b80ac83e845999e9f15bec369592d9d04649
**FAILED TO BOOTSTRAP** please scroll up and look for earlier error messages, there may be more than one

```

This using the update method:

```
./launcher stop discourse
git pull
./launcher rebuild discourse

```

This of course leads me back to my loop placing the 9.3 postgres template in my discourse.yml and bootstrap failing again due to apt errors.

I am attempting to disable HSTS now to see if I can get the app to rebuild that way.

---

_[View the full topic](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670)._