Atualização com erro: ERRO: deve ser proprietário da extensão vector (PG::InsufficientPrivilege)

Bug
,
1 
I, [2024-08-08T22:28:10.332254 #1]  INFO -- : \u003e cd /var/www/discourse \u0026\u0026 su discourse -c 'bundle exec rake db:migrate'
2024-08-08 22:28:18.660 UTC [1022] discourse@discourse ERROR:  must be owner of extension vector
2024-08-08 22:28:18.660 UTC [1022] discourse@discourse STATEMENT:  ALTER EXTENSION vector UPDATE TO '0.7.0';
rake aborted!
StandardError: An error has occurred, this and all later migrations canceled: (StandardError)

ERROR:  must be owner of extension 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 \u003cmain\u003e'
/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 \u003cmain\u003e'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.2.1/exe/rake:27:in `\u003ctop (required)\u003e'
/usr/local/bin/bundle:25:in `load'
/usr/local/bin/bundle:25:in `\u003cmain\u003e'

Caused by:
PG::InsufficientPrivilege: ERROR:  must be owner of extension vector (PG::InsufficientPrivilege)

Duas linhas se destacam:

  • 2024-08-08 22:28:18.660 UTC [1022] discourse@discourse ERROR: must be owner of extension 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: must be owner of extension vector (PG::InsufficientPrivilege)

Faz ±1-2 semanas desde minha última atualização, alguém consegue reproduzir isso ou tem algum conselho?

EDIT: Desabilitei o discourse-ai - reconstruindo sem problemas agora.

2 curtidas
2

Esta é uma instalação padrão com apenas um contêiner?

3

Sim, está. Instalei há alguns anos seguindo o guia oficial.

1 curtida
5
3 curtidas
6

Sim, ainda está lá — porque eu esqueci de verificar se isso foi mesclado ou se ainda está aberto :man_facepalming:

1 curtida
7

Já foi mesclado

8

Desculpe, mas isso significa que este problema foi resolvido?
Estou tendo um problema semelhante ao discutido aqui.

9

Sim, tente atualizar seu site por meio de uma reconstrução.

3 curtidas
10

Infelizmente, falhou.

Esta imagem exibe uma tela de computador com um editor de código de programação aberto, mostrando um script Python. (Legenda por IA)
Esta imagem exibe uma tela de computador com um editor de código de programação aberto, mostrando um script Python. (Legenda por IA)1360×768 54.2 KB

Mais informações foram coladas por mim em este tópico, se isso ajudar.
Também, por favor, note que o meu é uma configuração de 2 contêineres.

Também, se isso for 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 mim funcionou

1 curtida
12

Como sempre, se você tiver uma configuração de dois contêineres, precisará atualizar ambos.

1 curtida
13

Confirmo que a correção resolveu o problema para mim. Obrigado!

3 curtidas
14

Obrigado, eu não sabia disso.

Mas quando tentei inicializar meu contêiner ‘data’, recebi este erro:

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

Preciso parar meu contêiner ‘Web_only’ primeiro? Embora eu também tenha tentado fazer isso, como precaução.

15

Este tópico foi fechado automaticamente após 3 dias. Novas respostas não são mais permitidas.