I logged in. Haven’t updated in 11 months. Started with trying to upgrade the Docker Manager. It never seemed to complete. Next day the admin page was pretty much borked. I tried to do the ./launcher rebuild app. I get the 2025-10-30 20:04:52.144 UTC [1892] discourse@c_discourse ERROR: must …

[изображение] pfaffman: If you’ll look at the pg 15 topic it’ll tell you how to rename the backup directory that still has the pg 13 files. [изображение] Stew_Pid: That’s a long thread so let me make sure I’m looking at the correct thing. Use the 13 template mv /shared/postgres_data to …

If you haven’t seen the topic PostgreSQL 15 update - Announcements you might start there. It discusses a number of issues and recommendations.

Thanks. Too much to really grok it all but nothing seems like my problem. :frowning: The database seems to run during the rebuild process which is the strange part. At least from what I can tell in the stuff that scrolls by.

[изображение] Stew_Pid: Haven’t updated in 11 months. Started with trying to upgrade the Docker Manager. That’s mostly never going to work after 11 months. Your definitely need to do the postgres 15 upgrade, and that’s part of what’s wrong. It’s possible that that can switch to the postgres …

[изображение] Stew_Pid: must be owner of extension vector Is this a standard install ?

[изображение] RGJ: Is this a standard install ? Not if multisite is still considered unsupported. The issue seems to be when I installed it there was no user/password connected to the individual databases. That seems to change. That’s where the problem lies. I’ve tried to tinker a little …

Does this mean that the database actually starts during the install process? 2025-10-31 15:14:30.984 UTC [45] LOG: starting PostgreSQL 15.14 (Debian 15.14-1.pgdg12+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0 -14+deb12u1) 12.2.0, 64-bit 2025-10-31 15:14:30.984 UTC [45] LOG: listening…

Pgvector extension is either out of date or not set up on one of your databases. I have encountered this on a few installs a few months ago. It is very simple to resolve, You just need to update it. enter the db container, psql as discourse (or whatever is your db owner) and then choose each databa…

[изображение] Stew_Pid: 2025-10-30 20:04:52.144 UTC [1892] discourse@c_discourse ERROR: must be owner of extension vector 2025-10-30 20:04:52.144 UTC [1892] discourse@c_discourse STATEMENT: ALTER EXTENSION vector UPDATE TO ‘0.7.0’; Looks like the extension owner for the c_discourse database…

Any help on how I start the database to do this? That’s really the sticking point. EDIT: The only postgres files I find are of the /13. So I’m kind of in a state of limbo. Seems the database program upgraded but the database files didn’t. I’ve done some searches but nothing I’m comfortable wit…

You should be able to edit the app.yml and use the postgres 13 template and rebuild, as described in the PostgreSQL 15 update topic. Then you can rebuild. Then you can start the container. Then you can enter the container. Then you can do the pgvectkr stuff.

Upgrade failed. Database stopped. (multisite install)

Поддержка Самостоятельное хостинг

pfaffman (Jay Pfaffman) Разделил(а) эту тему 03.Ноябрь.2025 21:45:08 20

A post was merged into an existing topic: Database access issues after upgrade v3.5.2 → v3.6.0.beta2

Тема		Ответов	Просм.
Database access issues after upgrade v3.5.2 -> v3.6.0.beta2 Support	11	167	08.11.2025
Failing update Self-hosting	35	510	25.09.2025
PostgreSQL 15 update Announcements	111	4870	02.12.2025
Upgrade Failed from 2.7.0.beta1 to 2.7.0.beta3 Self-hosting	13	1954	15.02.2021
Help! Upgrade led to complete fail Self-hosting	8	1348	09.03.2021

Upgrade failed. Database stopped. (multisite install)

Связанные темы