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…

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…

[image] 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?

You could try: su - postgres /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main - replacing the 13 with your current version. Which is the command advertised on the process of a healthy install. No warranty with that though as I’ve not tested it! No don’t bother doing this, see fur…

thanks. I have version 12, but got the following error - su: invalid option – ‘D’ Try ‘su --help’ for more information.

[image] postmaster -D is a legal switch. Make sure you didn’t include the hyphen outside the code snippet?

btw, I’m wondering if your version 13 upgrade process failed. If so you might like to take a look at and potentially post in this Topic: PostgreSQL 13 update

Urgent, échec de la build mise à niveau UniqueViolation

Soutien Installation

merefield (Robert) Janvier 21, 2021, 7:59 15

Au fait, je me demande si votre processus de mise à niveau vers la version 13 a échoué.

Si c’est le cas, vous pourriez jeter un coup d’œil à ce sujet et éventuellement y poster : PostgreSQL 13 update

Sujet		Réponses	Vues
Upgrade Issues: Failed Upgrade due to Duplicate Key, Failed Snapshot Restore Self-hosting	7	1690	Avril 25, 2023
Upgrade failed with "duplicate key value violates unique constraint" error Self-hosting	18	2511	Mars 30, 2020
Upgrade Failed from 2.7.0.beta1 to 2.7.0.beta3 Self-hosting	13	2005	Février 15, 2021
Trouble updating discourse after some time - UPGRADE OF POSTGRES FAILED Support	6	148	Novembre 21, 2025
Docker error on command line upgrade (postgres?) Self-hosting	5	802	Juin 26, 2019

Urgent, échec de la build mise à niveau UniqueViolation

Sujets connexes