data cannot be rebuild ./launcher rebuild data x86_64 arch detected. Ensuring launcher is up to date Launcher is up-to-date 2.0.20250129-0720: Pulling from docker-hub-china/discourse-base Digest: sha256:d798a945ca4d31c29e5d263cdaf807bafab9b5f6737be0b1b852bea0063a3b91 Status: Image is up to date for…

I got the upgrade PostgreSQL15 Templates need to be used in sequence postgres.13.template.yml postgres.15.template.yml postgres.template.yml postgres.13.template.yml、postgres.15.template.yml file China network acceleration configuration run: - exec: cat /etc/os-release && psql --version - …

Your logs appear to be incomplete but the snippet below can provide a hint. socat[33] E connect(, AF=1 “/shared/postgres_run/.s.PGSQL.5432”, 36): Connection refused Are you also seeing the error below much lower in your log output? The source cluster was not shut down cleanly If so, you can …

[afbeelding] PostgreSQL 15 update Restart the old container with ./launcher start app. Wait a few minutes until it is back up. Are you seeing any errors from that first step?

I used the data.yml and web_only.yml methods

You can still follow the same instructions, but replace any occurrences of app or standalone with data.

Still not connected $ ./launcher enter data x86_64 arch detected. root@sober-data:/# export SVWAIT=300 sv stop nginx sv stop unicorn sv stop postgres exit fail: nginx: unable to change to service directory: file does not exist fail: unicorn: unable to change to service directory: file does not exis…

[afbeelding] sober: $ ./launcher enter data x86_64 arch detected. root@sober-data:/# This implies you were connected to the container. (Just ensure that the web_only container remains stopped during the rebuild of the data container.) ok: down: postgres: 0s, normally up This is the outp…

./launcher enter data x86_64 arch detected. root@sober-data:/# sv stop postgres ok: down: postgres: 0s, normally up root@sober-data:/# exit logout root@sober:/var/discourse$ ./launcher rebuild data x86_64 arch detected. Ensuring launcher is up to date Launcher is up-to-date Stopping old container…

[afbeelding] sober: initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. Is the rebuild stuck at this point? If so, cancel it and run this instead then post the results. ./launcher start data ./launche…

Thank you very much. Let me go back to the docker version and postgres.template.yml ./launcher rebuild data x86_64 arch detected. Ensuring launcher is up to date Launcher is up-to-date Stopping old container + /usr/bin/docker stop -t 600 data data 2.0.20250129-0720: Pulling from docker-hub-china/di…

PostgreSQL-update mislukt vanuit China

Ondersteuning

mwaniki (Mwaniki Wairungu) 6 februari 2025 om 05:48 4

Are you seeing any errors from that first step?

Topic		Antwoorden	Weergaven
Site Won't Start After Update Self-hosting	6	1147	29 juli 2018
PostgreSQL 15 update Announcements	107	6607	22 oktober 2025
Site offline after rebuild (4th Feb 2025) Support	16	506	6 februari 2025
PostgreSQL Stuck During Rebuilding Self-hosting	51	2143	4 september 2024
Manual upgrade failure due to postgres error Self-hosting	1	488	28 oktober 2020

PostgreSQL-update mislukt vanuit China

Gerelateerde topics