I tried to upgrade discourse and got the following message - I, [2021-01-21T18:39:25.045454 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' 2021-01-21 18:39:32.724 UTC [4051] discourse@discourse LOG: duration: 336.116 ms statement: UPDATE users SET locale …

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. rename postgres_data to postgres_data_new rename postgres_data_old to p…

Do you have any idea @merefield ? thanks! [이미지] Failed upgrade: UniqueViolation: duplicate key value violates unique constraint "data_explorer_queries_pkey" Self-hosting So restart the container? ./launcher start app Then you want something like: ./launche…

Hey. When an upgrade fails the container is left stopped. (Try to connect to your site via browser and you’ll see that’s the case) So you may have simply not started the latest working container. (Pre-upgrade) Do that with ./launcher start app then enter the container and attempt to jump into th…

Thanks, I did restart the container, any thought? I tried ./launcher enter app anything else I can try? ubuntu@:/var/discourse$ ./launcher start app WARNING: Docker version 17.05.0-ce deprecated … Nothing to do, your container has already started!

Did you get an error when entering the container?

No error, but when I did ./launcher logs app I got the following - ok: run: redis: (pid 47) 918s timeout: down: postgres: 1s, normally up, want up ok: run: redis: (pid 47) 925s timeout: down: postgres: 0s, normally up, want up ok: run: redis: (pid 47) 933s ok: run: postgres: (pid 1855) 0s su…

[이미지] vw_james: psql: error: could not connect to server: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket “/var/run/postgresql/.s.PGSQL.5432”? What’s the result of ps -ef | grep postgres?

root 38 35 0 19:09 ? 00:00:00 runsv postgres root 46 38 0 19:09 ? 00:00:00 svlogd /var/log/postgres root 2573 2571 0 19:31 ? 00:00:00 sv start postgres root 2575 2497 0 19:31 ? 00:00:00 grep postgres

Should I run it inside the container or just at the linux box?

Inside. Looks like it’s not running. You will need to restart it manually I suspect, as postgres user.

Do you know the quick command to restart it?

긴급, 업그레이드된 빌드 실패 UniqueViolation

지원 자체 호스팅

vw_james (james) 1월 21, 2021, 7:09오후 2

Do you have any idea @merefield ? thanks!

글		댓글	조회수
Upgrade Issues: Failed Upgrade due to Duplicate Key, Failed Snapshot Restore Self-hosting	7	1760	4월 25, 2023
Upgrade failed with "duplicate key value violates unique constraint" error Self-hosting	17	2654	2월 29, 2020
Upgrade Failed from 2.7.0.beta1 to 2.7.0.beta3 Self-hosting	13	2187	2월 15, 2021
Trouble updating discourse after some time - UPGRADE OF POSTGRES FAILED Support	5	255	11월 21, 2025
Docker error on command line upgrade (postgres?) Self-hosting	4	845	5월 27, 2019

긴급, 업그레이드된 빌드 실패 UniqueViolation

Related topics