I am single container and installed by official way here is the log Upgrading PostgreSQL from version 13 to 15 The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale "en_US.UTF-…

Could you try these steps? [image] PostgreSQL 15 update If the logs do not indicate that the database is shut down, you can start the old container again, enter with ./launcher enter app, run these commands and tail the logs again once done. export SVWAIT=300 sv stop nginx sv stop unicorn sv st…

[image] Yt.w: The source cluster was not shut down cleanly. This means you need to [image] Yt.w: You can run ./launcher start app to restart your app in the meanwhile and then ./launcher stop app afterwards and try a rebuild again.

Hello, I did 1 ./launcher start app 2 ./launcher stop app 3 ./launcher rebuild app and the error was same

I may found the reason, after I run ./launcher stop app The DB system did not shut down. I waited for 3 mins already. any ideas? 2025-02-11 19:24:08.044 UTC [550] LOG: listening on IPv4 address "0.0.0.0", port 5432 2025-02-11 19:24:08.044 UTC [550] LOG: listening on IPv6 address "::", port 5432…

You want to start the container, wait for the database to be on a slow period and try again.

There are almost no user is using my discourse instance now. so I guess the database is on a slow period…

Impossible de reconstruire l'application car la mise à niveau de Postgres a échoué

Assistance produit Installation

Yt.w Février 12, 2025, 5:13 8

Ça marche. Merci beaucoup !

Sujet		Réponses	Vues
Discourse rebuild fails due to unclean shutdown Product Support	3	351	Février 4, 2025
Cannot rebuild app, Product Support	2	243	Février 3, 2025
Upgrade of postgres failed Self-hosting	1	1185	Septembre 25, 2020
Update fails with error postgres already running stop container Self-hosting	2	272	Août 30, 2024
PostgreSQL 15 update Announcements	107	8294	Octobre 22, 2025

Impossible de reconstruire l'application car la mise à niveau de Postgres a échoué

Sujets connexes