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 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’; But the database is stopped so the fixes I saw don’t work. 2025-10-31 00:27:40.021 UTC [662] FATAL: database files are incompatible with server 2025-10-31 00:27:40.021 UTC [662] DETAIL: The data directory was initialized by PostgreSQL version 15, which is not compatible with this version 13.16 (Debian 13.16-1.pgdg120+1). But root@main-app:/var/lib/postgresql# pg_config --version PostgreSQL 16.4 (Debian 16.4-1.pgdg120+1) EDIT: It looks like the DB is still in 13 format? root@main-app:/var/lib/postgresql# ls 13 take-database-backup

[imagem] 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. [imagem] 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 something like /shared/postgres_data.bak mv /shared/postgres_data_old to /shared/postgres_data Since I moved them as root I had to chown and then chmod the files. I didn’t document these but the error output give it. [imagem] itsbhanusharma: ALTER EXTENSION vector UPDATE;

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.

[imagem] 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 13 and get things going again before doing the upgrade.

[imagem] Stew_Pid: must be owner of extension vector Is this a standard install ?

[imagem] 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 with it by adding a user and then a user with a blank password but that didn’t help My config versus the new sample config: secondsite: adapter: postgresql database: b_discourse pool: 25 timeout: 5000 db_id: 2 host_names: forum.xxx.com mlp: adapter: postgresql database: discourse_mlp username: discourse_mlp password: applejack host: dbhost pool: 5 timeout: 5000 host_names: discourse.equestria.com discourse.equestria.internal

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 on IPv4 address “0.0.0.0”, port 5432 2025-10-31 15:14:30.984 UTC [45] LOG: listening on IPv6 address “::”, port 5432 2025-10-31 15:14:31.055 UTC [45] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432” 2025-10-31 15:14:31.135 UTC [56] LOG: database system was shut down at 2025-10-31 02:08:49 UTC 2025-10-31 15:14:31.199 UTC [45] LOG: database system is ready to accept connections I, [2025-10-31T15:14:35.760150 #1] INFO – : I, [2025-10-31T15:14:35.760557 #1] INFO – : > /usr/local/bin/create_db 2025-10-31 15:14:35.912 UTC [63] postgres@postgres ERROR: database “discourse” already exists 2025-10-31 15:14:35.912 UTC [63] postgres@postgres STATEMENT: CREATE DATABASE discourse; createdb: error: database creation failed: ERROR: database “discourse” already exists 2025-10-31 15:14:36.060 UTC [66] postgres@discourse ERROR: role “discourse” already exists 2025-10-31 15:14:36.060 UTC [66] postgres@discourse STATEMENT: create user discourse; ERROR: role “discourse” already exists NOTICE: extension “hstore” already exists, skipping NOTICE: extension “pg_trgm” already exists, skipping NOTICE: extension “vector” already exists, skipping NOTICE: version “0.8.1” of extension “vector” is already installed NOTICE: extension “hstore” already exists, skipping NOTICE: extension “pg_trgm” already exists, skipping NOTICE: extension “vector” already exists, skipping NOTICE: version “0.8.1” of extension “vector” is already installed I, [2025-10-31T15:14:37.265035 #1] INFO – : GRANT ALTER SCHEMA CREATE EXTENSION CREATE EXTENSION CREATE EXTENSION ALTER EXTENSION CREATE EXTENSION CREATE EXTENSION CREATE EXTENSION ALTER EXTENSION UPDATE 0 I, [2025-10-31T15:14:37.265325 #1] INFO – : > echo postgres installed! I, [2025-10-31T15:14:37.270967 #1] INFO – : postgres installed! I, [2025-10-31T15:14:37.271578 #1] INFO – : > sudo -u postgres createdb b_discourse || exit 0 2025-10-31 15:14:37.380 UTC [104] postgres@postgres ERROR: database “b_discourse” already exists 2025-10-31 15:14:37.380 UTC [104] postgres@postgres STATEMENT: CREATE DATABASE b_discourse; createdb: error: database creation failed: ERROR: database “b_discourse” already exists I, [2025-10-31T15:14:37.385149 #1] INFO – : I, [2025-10-31T15:14:37.385968 #1] INFO – : > sudo -u postgres psql b_discourse I, [2025-10-31T15:14:37.390476 #1] INFO – : grant all privileges on database b_discourse to discourse; I, [2025-10-31T15:14:37.515870 #1] INFO – : > sudo -u postgres createdb c_discourse || exit 0 2025-10-31 15:14:37.625 UTC [111] postgres@postgres ERROR: database “c_discourse” already exists 2025-10-31 15:14:37.625 UTC [111] postgres@postgres STATEMENT: CREATE DATABASE c_discourse; createdb: error: database creation failed: ERROR: database “c_discourse” already exists I, [2025-10-31T15:14:37.629387 #1] INFO – : I, [2025-10-31T15:14:37.630145 #1] INFO – : > sudo -u postgres psql c_discourse I, [2025-10-31T15:14:37.634672 #1] INFO – : grant all privileges on database c_discourse to discourse; I, [2025-10-31T15:14:37.758171 #1] INFO – : > /bin/bash -c ‘sudo -u postgres psql b_discourse /bin/bash -c ‘sudo -u postgres psql b_discourse /bin/bash -c ‘sudo -u postgres psql b_discourse <<< “create extension if not exists pg_trgm;”’ NOTICE: extension “pg_trgm” already exists, skipping I, [2025-10-31T15:14:38.117879 #1] INFO – : CREATE EXTENSION 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 on IPv4 address “0.0.0.0”, port 5432 2025-10-31 15:14:30.984 UTC [45] LOG: listening on IPv6 address “::”, port 5432 2025-10-31 15:14:31.055 UTC [45] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432” 2025-10-31 15:14:31.135 UTC [56] LOG: database system was shut down at 2025-10-31 02:08:49 UTC 2025-10-31 15:14:31.199 UTC [45] LOG: database system is ready to accept connections I, [2025-10-31T15:14:35.760150 #1] INFO – : I, [2025-10-31T15:14:35.760557 #1] INFO – : > /usr/local/bin/create_db 2025-10-31 15:14:35.912 UTC [63] postgres@postgres ERROR: database “discourse” already exists 2025-10-31 15:14:35.912 UTC [63] postgres@postgres STATEMENT: CREATE DATABASE discourse; createdb: error: database creation failed: ERROR: database “discourse” already exists 2025-10-31 15:14:36.060 UTC [66] postgres@discourse ERROR: role “discourse” already exists 2025-10-31 15:14:36.060 UTC [66] postgres@discourse STATEMENT: create user discourse; ERROR: role “discourse” already exists NOTICE: extension “hstore” already exists, skipping NOTICE: extension “pg_trgm” already exists, skipping NOTICE: extension “vector” already exists, skipping NOTICE: version “0.8.1” of extension “vector” is already installed NOTICE: extension “hstore” already exists, skipping NOTICE: extension “pg_trgm” already exists, skipping NOTICE: extension “vector” already exists, skipping NOTICE: version “0.8.1” of extension “vector” is already installed I, [2025-10-31T15:14:37.265035 #1] INFO – : GRANT ALTER SCHEMA CREATE EXTENSION CREATE EXTENSION CREATE EXTENSION ALTER EXTENSION CREATE EXTENSION CREATE EXTENSION CREATE EXTENSION ALTER EXTENSION UPDATE 0 I, [2025-10-31T15:14:37.265325 #1] INFO – : > echo postgres installed! I, [2025-10-31T15:14:37.270967 #1] INFO – : postgres installed! I, [2025-10-31T15:14:37.271578 #1] INFO – : > sudo -u postgres createdb b_discourse || exit 0 2025-10-31 15:14:37.380 UTC [104] postgres@postgres ERROR: database “b_discourse” already exists 2025-10-31 15:14:37.380 UTC [104] postgres@postgres STATEMENT: CREATE DATABASE b_discourse; createdb: error: database creation failed: ERROR: database “b_discourse” already exists I, [2025-10-31T15:14:37.385149 #1] INFO – : I, [2025-10-31T15:14:37.385968 #1] INFO – : > sudo -u postgres psql b_discourse I, [2025-10-31T15:14:37.390476 #1] INFO – : grant all privileges on database b_discourse to discourse; I, [2025-10-31T15:14:37.515870 #1] INFO – : > sudo -u postgres createdb c_discourse || exit 0 2025-10-31 15:14:37.625 UTC [111] postgres@postgres ERROR: database “c_discourse” already exists 2025-10-31 15:14:37.625 UTC [111] postgres@postgres STATEMENT: CREATE DATABASE c_discourse; createdb: error: database creation failed: ERROR: database “c_discourse” already exists I, [2025-10-31T15:14:37.629387 #1] INFO – : I, [2025-10-31T15:14:37.630145 #1] INFO – : > sudo -u postgres psql c_discourse I, [2025-10-31T15:14:37.634672 #1] INFO – : grant all privileges on database c_discourse to discourse; I, [2025-10-31T15:14:37.758171 #1] INFO – : > /bin/bash -c ‘sudo -u postgres psql b_discourse /bin/bash -c ‘sudo -u postgres psql b_discourse /bin/bash -c ‘sudo -u postgres psql b_discourse <<< “create extension if not exists pg_trgm;”’ NOTICE: extension “pg_trgm” already exists, skipping I, [2025-10-31T15:14:38.117879 #1] INFO – : CREATE EXTENSION

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 database and run ALTER EXTENSION vector UPDATE; Ps: it seems as if your setup is a bit different, the above will only work if you have a separate data container.

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 with short of trying to copy the files out and playing with them. 2025-10-31 00:27:40.021 UTC [662] FATAL: database files are incompatible with server 2025-10-31 00:27:40.021 UTC [662] DETAIL: The data directory was initialized by PostgreSQL version 15, which is not compatible with this version 13.16 (Debian 13.16-1.pgdg120+1).

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.

Falha na atualização. Banco de dados parado. (instalação multisite)

Suporte ao Produto Instalação

Stew_Pid 2 Novembro , 2025 18:24 19

Link para o problema atual.

Tópico		Respostas	Vistas
Database access issues after upgrade v3.5.2 -> v3.6.0.beta2 Product Support	8	473	8 Novembro , 2025
Failing update Self-hosting	32	1145	26 Agosto , 2025
PostgreSQL 15 update Announcements	107	8653	22 Outubro , 2025
Upgrade Failed from 2.7.0.beta1 to 2.7.0.beta3 Self-hosting	13	2375	15 Fevereiro , 2021
Help! Upgrade led to complete fail Self-hosting	7	1571	9 Março , 2021

Falha na atualização. Banco de dados parado. (instalação multisite)

Related topics