Errore dopo l'aggiornamento di Docker Manager a ea174f7e

xkhalid · 23 Ottobre 2024, 6:18pm

Gentili Signori,

Ho un’istanza Discourse self-hosted e, quando ho tentato di aggiornare Docker Manager alla versione ea174f7e, ho riscontrato il seguente errore:

Docker Manager: FAILED TO UPGRADE
#<ActiveRecord::StatementInvalid:"PG::UndefinedColumn: ERROR:  column users.password_hash does not exist
LINE 1: ...ed_at", "users"."name", "users"."last_posted_at", "users"."p...
                                                             ^
">
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-3.3.1/lib/patches/db/pg.rb:69:in `exec_params'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-3.3.1/lib/patches/db/pg.rb:69:in `exec_params'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:894:in `block (2 levels) in exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:1027:in `block in with_raw_connection'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-7.1.4/lib/active_support/concurrency/null_lock.rb:9:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:999:in `with_raw_connection'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:893:in `block in exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-7.1.4/lib/active_support/notifications/instrumenter.rb:58:in `instrument'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:1142:in `log'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:892:in `exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:872:in `execute_and_clear'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/postgresql/database_statements.rb:64:in `internal_exec_query'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:630:in `select'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:71:in `select_all'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/connection_adapters/abstract/query_cache.rb:115:in `select_all'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/querying.rb:62:in `_query_by_sql'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/querying.rb:51:in `find_by_sql'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/statement_cache.rb:150:in `execute'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/core.rb:431:in `cached_find_by'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-7.1.4/lib/active_record/core.rb:252:in `find'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:261:in `log_version_upgrade'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:136:in `upgrade'
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:19:in `block in <main>'
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:6:in `fork'
/var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:6:in `<main>'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/commands/runner/runner_command.rb:41:in `load'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/commands/runner/runner_command.rb:41:in `block in perform'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-7.1.4/lib/active_support/execution_wrapper.rb:92:in `wrap'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/commands/runner/runner_command.rb:40:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.3.2/lib/thor/command.rb:28:in `run'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.3.2/lib/thor/invocation.rb:127:in `invoke_command'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/command/base.rb:178:in `invoke_command'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/thor-1.3.2/lib/thor.rb:538:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/command/base.rb:73:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/command.rb:71:in `block in invoke'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/command.rb:149:in `with_argv'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/command.rb:69:in `invoke'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.1.4/lib/rails/commands.rb:18:in `<main>'
/usr/local/lib/ruby/3.3.0/bundled_gems.rb:74:in `require'
/usr/local/lib/ruby/3.3.0/bundled_gems.rb:74:in `block (2 levels) in replace_require'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
bin/rails:18:in `<main>'

Tuttavia, nella pagina di aggiornamento, sembra che tutto vada bene:

C’è qualcos’altro che devo fare?

Grazie!

ajtowns · 25 Ottobre 2024, 6:21am

Ho ricevuto lo stesso errore con la barra di avanzamento dell’aggiornamento interrotta, forse al 90%, 95% del completamento. Tutto è stato segnalato come aggiornato in seguito, e poi successivamente l’aggiornamento di Discourse a un nuovo commit sembra aver funzionato bene.

otseng · 26 Ottobre 2024, 3:21pm

Ho avuto lo stesso errore. Ma dopo aver eseguito nuovamente l’aggiornamento, sembra che sia stato aggiornato correttamente.

xkhalid · 26 Ottobre 2024, 8:55pm

CC: @sam @ella

Qualsiasi aiuto o suggerimento riguardo all’errore dopo l’aggiornamento di Docker Manager? Per me ora funziona tutto bene, ma sono preoccupato che il prossimo aggiornamento possa causare qualche problema.

ella · 28 Ottobre 2024, 4:43pm

Grazie per la segnalazione! Ci stiamo occupando della cosa.

david · 28 Ottobre 2024, 5:03pm

L’errore si verifica mentre docker_manager tenta di registrare l’aggiornamento nel staff-action-log. Questa PR dovrebbe risolvere il problema:

github.com/discourse/docker_manager

FIX: Minimize database access following `db:migrate`

main ← db-access

opened 04:57PM - 28 Oct 24 UTC

davidtaylorhq

+3 -1

The upgrade process was triggering the database migrations, and then calling `Us…er.find()`. This is problematic because the `users` table may have been changed by the migrations, and accessing it with the 'old code' will raise an exception. This commit tweaks the Upgrader so that it loads the user object into memory **before** running database migrations.

xkhalid · 29 Ottobre 2024, 7:35pm

Grazie @david

david · 28 Novembre 2024, 7:36pm

Questo argomento è stato chiuso automaticamente 30 giorni dopo l’ultima risposta. Non sono più consentite nuove risposte.

Argomento		Risposte	Visualizzazioni
Can't upgrade: "Docker Manager: FAILED TO UPGRADE" Installation docker-manager	1	52	Luglio 26, 2024
Discourse Docker Manager Plugin official , docker-manager	16	10164	Agosto 24, 2025
Failed upgrade: docker manager Support	5	465	Gennaio 19, 2024
Upgrade of docker manager beta7 >> beta9 fails Installation	7	1126	Gennaio 8, 2020
Upgrade docker_manager stuck - 2.2.0.beta4 Support	12	1693	Dicembre 16, 2018

Errore dopo l'aggiornamento di Docker Manager a ea174f7e

Argomenti correlati