Urgent, upgraded build failed UniqueViolation

installation
21

Bingo … ok suggest you post in the upgrade Topic :+1:

1 Like
22

Thinking about this, outside your container try to rename your old postgres file and renaming the new one _new

Then try to restart the service within docker

files are in /var/discourse/shared/standalone outside the container.

  1. rename postgres_data to postgres_data_new
  2. rename postgres_data_old to postgres_data
  3. restart service inside container as above
  4. check it’s started again with logs inspection.
  5. If good, you can proceed with fixing the data.
3 Likes
23

Hi @merefield replying here on behalf of @vw_james (new account, seems like he’s reached a limit of posts for now).

That did the trick for us, the site is back up with the old data. We’ll figure out what happens next when we try to upgrade again. Thanks a million for your help!

3 Likes
24

Pleasure, glad that worked!

Btw for anyone reading this solution you surely might rename that file within docker too as the path is mounted.

1 Like
25

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.