### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [November 8, 2016, 4:57pm UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/2 "2016-11-08T16:57:17Z")
A current `app.yml` should be using:
```
templates:
- "templates/postgres.template.yml"
- "templates/redis.template.yml"
- "templates/web.template.yml"
- "templates/web.ratelimited.template.yml"
## Uncomment these two lines if you wish to add Lets Encrypt (https)
- "templates/web.ssl.template.yml"
- "templates/web.letsencrypt.ssl.template.yml"
```
Why are you using PostgreSQL 9.3? Take a backup, fix templates, rebuild and, if needed, restore the backup.
---
### Author:  [@CamilleRoux](https://meta.discourse.org/u/CamilleRoux)
#### Post date: [November 8, 2016, 5:05pm UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/3 "2016-11-08T17:05:32Z")
I choose the 9.3 because there was some bug with the LANG value.
Now if I’m using `templates/postgres.template.yml`, I get the following message in logs:
```
Failure, exiting
-------------------------------------------------------------------------------------
UPGRADE OF POSTGRES FAILED
You are going to need to export your data and import into a clean instance:
In containers/app.yml: Change "templates/postgres.template.yml" TO "templates/postgres.9.3.template.yml"
Run ./launcher rebuild app again
When your instance is running:
Run ./launcher enter app
Run cd /shared/postgres_backup && sudo -u postgres pg_dump discourse > backup.db
Undo the postgres template in your container config
Run: ./launcher stop app
Run: sudo mv /var/discourse/shared/standalone/postgres_data /var/discourse/shared/standalone/postgres_data_old
Run: ./launcher rebuild app
Run: ./launcher enter app
Run: cd /shared/postgres_backup
Run: sv stop unicorn
Run: sudo -iu postgres dropdb discourse
Run: sudo -iu postgres createdb discourse
Run: sudo -iu postgres psql discourse < backup.db
Run: exit
Run: ./launcher rebuild app
FAILED
--------------------
Pups::ExecError: /root/upgrade_postgres failed with return #
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params "/root/upgrade_postgres"
ebd56652d59e7b6edf01ea0d356cf73719b37fc918a87d6f6db292bf18e6aa68
**FAILED TO BOOTSTRAP** please scroll up and look for earlier error messages, there may be more than one
```
But, because `rebuild` is failing with the template `postgres.9.3.template.yml`, I don’t know what to do…
---
### Author:  [@sphyden](https://meta.discourse.org/u/sphyden)
#### Post date: [December 5, 2016, 5:03pm UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/4 "2016-12-05T17:03:33Z")
Im running into the same catch 22. The failed bootstrap give the instructions, but instructions can’t be run because the app will not rebuild.
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [December 5, 2016, 5:08pm UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/5 "2016-12-05T17:08:23Z")
First of all, take a backup and download it!
Then follow this:
```plaintext
cd /var/discourse
mv shared shared_old
```
Then edit app.yml, removing postgres version from it. After the editing the first lines should look like this:
```plaintext
## this is the all-in-one, standalone Discourse Docker container template
##
## After making changes to this file, you MUST rebuild
## /var/discourse/launcher rebuild app
##
## BE *VERY* CAREFUL WHEN EDITING!
## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNMENT!
## visit http://www.yamllint.com/ to validate this file as needed
templates:
- "templates/postgres.template.yml"
- "templates/redis.template.yml"
- "templates/web.template.yml"
- "templates/web.ratelimited.template.yml"
## Uncomment these two lines if you wish to add Lets Encrypt (https)
...
```
Then `./launcher rebuild app`, create an admin, upload a backup and restore. Just make sure to have plenty of space.
This procedure isn’t the fastest, but will work to restore a broken Discourse from any point to a usable and working install.
---
### Author:  [@sphyden](https://meta.discourse.org/u/sphyden)
#### Post date: [December 7, 2016, 7:45pm UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/6 "2016-12-07T19:45:55Z")
I am migrating my companies instance of discourse from CentOS 6 to CentOS 7 host. I can no longer update Discourse on Cent 6 because there is no new Docker versions. The first thing that I tried is what you mention above. I can import my backup, and successfully restore my data. The catch is I am no longer able to log into the site. Its in some weird state that the new instance thinks that I am logged in from the old instance, causing a log in loop on the new instance. I tried to use the api gem to force log myself out, but you need admin priv’s to do this. I cannot log in, in any form or fashion on the new instance to use the log out API call.
After that, I decided to attempt to simply stand up a new instance, and sync my standalone dir. on top of the new one, considering you offer a psql 9.3 template. Unfortunately I cannot bootstrap with the 9.3 template due to the apt-get errors mentioned above. If I bootstrap with the vanilla postgres template, I get schema errors because my old instance was running on 9.3.
I guess my next option will be to import the old Docker container via registry, and sync over the entire old “var/docker” directory to my new server, then fingers crossed when I attempt to actually update the instance.
Please let me know if there is anything else I can try here.
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [December 7, 2016, 8:04pm UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/7 "2016-12-07T20:04:42Z")
> [@sphyden](#):
>
> I am migrating my companies instance of discourse from CentOS 6 to CentOS 7 host. I can no longer update Discourse on Cent 6 because there is no new Docker versions. The first thing that I tried is what you mention above. I can import my backup, and successfully restore my data. The catch is I am no longer able to log into the site. Its in some weird state that the new instance thinks that I am logged in from the old instance, causing a log in loop on the new instance. I tried to use the api gem to force log myself out, but you need admin priv’s to do this. I cannot log in, in any form or fashion on the new instance to use the log out API call.
Try to logout trough rails console:
```plaintext
u = User.find_by_id(YOUR_ID_HERE)
u.update_attribute auth_token: nil
```
---
### Author:  [@sphyden](https://meta.discourse.org/u/sphyden)
#### Post date: [December 8, 2016, 2:40pm UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/8 "2016-12-08T14:40:03Z")
Is there a way that I can do this will all users simultaneously? Also, I can’t seem to find userids on our current production instance.
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [December 8, 2016, 4:31pm UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/9 "2016-12-08T16:31:08Z")
Something like
```plaintext
User.update_all(auth_token: nil)
```
should work.
---
### Author:  [@sphyden](https://meta.discourse.org/u/sphyden)
#### Post date: [December 8, 2016, 5:20pm UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/10 "2016-12-08T17:20:49Z")
> [@Falco](#):
>
> User.update\_all(auth\_token: nil)
I just stood up a new instance of Discourse, imported and restored to a backup of my production instance via the web Admin panel. At that point, all of my data shows up and the forum looks as it should, BUT I get stuck in the log in look explained earlier.
I tried the rails command quoted above, with the following return:
> [1] pry(main)\> User.update\_all(auth\_token: nil)
> =\> 1884
After that, I attempt to log in to the forum via web again, and again get the log in loop. It successfully authenticates, but never acts as If i am logged in.
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [December 8, 2016, 5:45pm UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/11 "2016-12-08T17:45:08Z")
Do you have some sort of outside reverse proxy? Is SSL enabled?
---
### Author:  [@sphyden](https://meta.discourse.org/u/sphyden)
#### Post date: [December 8, 2016, 6:21pm UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/12 "2016-12-08T18:21:04Z")
I have SSL enabled on my production instance, but not the current test instance. The web.ssl.template is being used in production, and commented out in test.
---
### Author:  [@sphyden](https://meta.discourse.org/u/sphyden)
#### Post date: [December 8, 2016, 8:01pm UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/13 "2016-12-08T20:01:41Z")
I’ve confirmed that the auth\_token for at least my user is nil. Still unable to log in.
```
=> #
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [December 8, 2016, 9:04pm UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/14 "2016-12-08T21:04:53Z")
Can you share a link?
If you had HSTS before this can wreak havoc.
---
### Author:  [@sphyden](https://meta.discourse.org/u/sphyden)
#### Post date: [December 8, 2016, 9:50pm UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/15 "2016-12-08T21:50:09Z")
I will work on getting the site opened up. In the mean time, I did find this in my production log, from attempted log in’s:
```
Started GET "/session/csrf?_=1481229888046" for ip at 2016-12-08 20:46:39 +0000
Processing by SessionController#csrf as */*
Parameters: {"_"=>"1481229888046"}
Completed 200 OK in 1ms (Views: 0.2ms | ActiveRecord: 0.0ms)
Started POST "/session" for ip at 2016-12-08 20:46:39 +0000
Processing by SessionController#create as */*
Parameters: {"login"=>"chu@phmgmt.com", "password"=>"[FILTERED]"}
Can't verify CSRF token authenticity
Rendered text template (0.0ms)
Filter chain halted as :verify_authenticity_token rendered or redirected
Completed 403 Forbidden in 1ms (Views: 0.3ms | ActiveRecord: 0.0ms)
```
---
### Author:  [@sphyden](https://meta.discourse.org/u/sphyden)
#### Post date: [December 13, 2016, 4:52pm UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/16 "2016-12-13T16:52:15Z")
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 #
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.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [December 14, 2016, 7:23am UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/17 "2016-12-14T07:23:46Z")
You got to follow the [manual backup / restore step](https://github.com/discourse/discourse_docker/blob/master/templates/postgres.template.yml#L71-L113) documented there if the automatic upgrade fails.
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [June 8, 2024, 12:45pm UTC](https://meta.discourse.org/t/errors-were-encountered-while-processing-postgresql-contrib-9-5/52670/18 "2024-06-08T12:45:07Z")
This topic was automatically closed after 2768 days. New replies are no longer allowed.