Actualización fallida: ERROR: debe ser propietario de la extensión vector (PG::InsufficientPrivilege)

Error
,
1 
I, [2024-08-08T22:28:10.332254 #1]  INFO -- : cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate'
2024-08-08 22:28:18.660 UTC [1022] discourse@discourse ERROR:  debe ser el propietario de la extensión vector
2024-08-08 22:28:18.660 UTC [1022] discourse@discourse STATEMENT:  ALTER EXTENSION vector UPDATE TO '0.7.0';
rake aborted!
StandardError: Ha ocurrido un error, esta y todas las migraciones posteriores se cancelaron: (StandardError)

ERROR:  debe ser el propietario de la extensión vector
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-3.3.1/lib/patches/db/pg.rb:110:in `exec'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-3.3.1/lib/patches/db/pg.rb:110:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.5.0/lib/mini_sql/postgres/connection.rb:202:in `run'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.5.0/lib/mini_sql/active_record_postgres/connection.rb:38:in `block in run'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.5.0/lib/mini_sql/active_record_postgres/connection.rb:34:in `block in with_lock'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-7.1.3.4/lib/active_support/concurrency/null_lock.rb:9:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.5.0/lib/mini_sql/active_record_postgres/connection.rb:34:in `with_lock'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.5.0/lib/mini_sql/active_record_postgres/connection.rb:38:in `run'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.5.0/lib/mini_sql/postgres/connection.rb:181:in `exec'
/var/www/discourse/plugins/discourse-ai/db/migrate/20240611170904_upgrade_pgvector_070.rb:10:in `up'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.3.4/lib/active_record/migration.rb:989:in `public_send'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.3.4/lib/active_record/migration.rb:989:in `exec_migration'
/var/www/discourse/lib/freedom_patches/schema_migration_details.rb:8:in `block in exec_migration'
/var/www/discourse/lib/freedom_patches/schema_migration_details.rb:8:in `exec_migration'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.3.4/lib/active_record/migration.rb:970:in `block (2 levels) in migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.3.4/lib/active_record/migration.rb:969:in `block in migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.3.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:227:in `with_connection'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.3.4/lib/active_record/migration.rb:968:in `block in migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.3.4/lib/active_record/migration.rb:1600:in `with_advisory_lock'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.3.4/lib/active_record/migration.rb:1448:in `block in migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.3.4/lib/active_record/migration.rb:1600:in `with_advisory_lock'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.3.4/lib/active_record/migration.rb:1448:in `migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.3.4/lib/active_record/migration.rb:1274:in `up'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.3.4/lib/active_record/migration.rb:1249:in `migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.3.4/lib/active_record/tasks/database_tasks.rb:243:in `migrate'
/var/www/discourse/lib/tasks/db.rake:259:in `block (2 levels) in <main>'
/var/www/discourse/lib/distributed_mutex.rb:53:in `block in synchronize'
/var/www/discourse/lib/distributed_mutex.rb:49:in `synchronize'
/var/www/discourse/lib/distributed_mutex.rb:49:in `synchronize'
/var/www/discourse/lib/distributed_mutex.rb:34:in `synchronize'
/var/www/discourse/lib/tasks/db.rake:234:in `block in <main>'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.2.1/exe/rake:27:in `<top (required)>'
/usr/local/bin/bundle:25:in `load'
/usr/local/bin/bundle:25:in `<main>'

Caused by:
PG::InsufficientPrivilege: ERROR:  debe ser el propietario de la extensión vector (PG::InsufficientPrivilege)

Dos líneas destacan:

  • 2024-08-08 22:28:18.660 UTC [1022] discourse@discourse ERROR: debe ser el propietario de la extensión vector
    2024-08-08 22:28:18.660 UTC [1022] discourse@discourse STATEMENT: ALTER EXTENSION vector UPDATE TO ‘0.7.0’;
    rake aborted!
  • PG::InsufficientPrivilege: ERROR: debe ser el propietario de la extensión vector (PG::InsufficientPrivilege)

Han pasado ±1-2 semanas desde mi última actualización, ¿alguien puede reproducir esto o tiene algún consejo?

EDIT: Deshabilité discourse-ai - ahora se está reconstruyendo sin problemas.

2 Me gusta
2

¿Esta es una instalación estándar con solo un contenedor?

3

Sí, lo está, instalado hace unos años usando la guía oficial.

1 me gusta
5
3 Me gusta
6

Sí, todavía está ahí, porque olvidé comprobar si esto está fusionado o todavía está abierto :man_facepalming:

1 me gusta
7

Ya está fusionado

8

Lo siento, ¿pero significa que este problema está resuelto?
Tengo un problema similar al discutido aquí.

9

Sí, intenta actualizar tu sitio mediante una reconstrucción.

3 Me gusta
10

Lamentablemente, falló.

Esta imagen muestra una pantalla de computadora con un editor de código de programación abierto, mostrando un script de Python. (Subtitulado por IA)
Esta imagen muestra una pantalla de computadora con un editor de código de programación abierto, mostrando un script de Python. (Subtitulado por IA)1360×768 54.2 KB

Se proporcionó más información en este tema, si eso ayuda.
También, por favor, tenga en cuenta que el mío es una configuración de 2 contenedores.

Además, si eso está relacionado:

:/var/www/discourse# LOAD_PLUGINS=1 bundle exec rake db:migrate
fatal: detected dubious ownership in repository at '/var/www/discourse'
To add an exception for this directory, call:
     git config --global --add safe.directory /var/www/discourse
11

Para mí funcionó

1 me gusta
12

Como siempre, si tienes una configuración de dos contenedores, necesitas actualizar ambos.

1 me gusta
13

Confirmo que la corrección solucionó el problema para mí. ¡Gracias!

3 Me gusta
14

Gracias, no lo sabía.

Pero cuando intenté iniciar mi contenedor ‘data’, me sale este error:

The image displays a computer screen with a terminal showing the output of a command, which seems to be related to software development, specifically working with a database or a server. The terminal output includes text that appears to be from a command-line interface, possibly from a software package like PostgreSQL or a configuration file. The text has various lines of code or commands, with some lines highlighted, indicating the importance of those lines. The content of the terminal output includes commands such as "CREATE TABLE," "INSERT INTO," and "SELECT," which are commonly used in SQL for creating, modifying, and querying database tables. The image captures the essence of a developer's workspace, where they might be working on a database setup or a script that interacts with a database. (Captioned by AI)
The image displays a computer screen with a terminal showing the output of a command, which seems to be related to software development, specifically working with a database or a server. The terminal output includes text that appears to be from a command-line interface, possibly from a software package like PostgreSQL or a configuration file. The text has various lines of code or commands, with some lines highlighted, indicating the importance of those lines. The content of the terminal output includes commands such as "CREATE TABLE," "INSERT INTO," and "SELECT," which are commonly used in SQL for creating, modifying, and querying database tables. The image captures the essence of a developer's workspace, where they might be working on a database setup or a script that interacts with a database. (Captioned by AI)1360×768 44 KB

¿Necesito detener primero mi contenedor ‘Web_only’? Aunque también lo he intentado, como precaución.

15

Este tema se cerró automáticamente después de 3 días. Ya no se permiten nuevas respuestas.