L'aggiornamento da 2.9.0.beta14 a 3.0.0.beta15 fallisce

Installazione
1

Non ho trovato argomenti quando ho cercato “upgrade failed” che menzionassero questo aggiornamento di versione.

Ho ricevuto la notifica e questa è un’istanza semplice senza alcuna attività utente oltre agli amministratori. Utilizzo questa installazione per testare le funzionalità prima di distribuirle su quella effettiva.

Facendo clic sul pulsante di aggiornamento dal pannello di amministrazione e quindi su “start upgrade” è stato restituito questo errore:

********************************************************
*** Please be patient, next steps might take a while ***
********************************************************
Cycling Unicorn, to free up memory
Restarting unicorn pid: 548
Waiting for Unicorn to reload.
Waiting for Unicorn to reload..
Waiting for Unicorn to reload...
Waiting for Unicorn to reload....
Waiting for Unicorn to reload.....
Waiting for Unicorn to reload......
Waiting for Unicorn to reload.......
Waiting for Unicorn to reload........
Waiting for Unicorn to reload.........
Waiting for Unicorn to reload..........
Waiting for Unicorn to reload..........
Docker Manager: FAILED TO UPGRADE
#<Redis::TimeoutError: Connection timed out>
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis/connection/ruby.rb:58:in `block in _read_from_socket'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis/connection/ruby.rb:54:in `loop'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis/connection/ruby.rb:54:in `_read_from_socket'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis/connection/ruby.rb:47:in `gets'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis/connection/ruby.rb:382:in `read'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis/client.rb:311:in `block in read'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis/client.rb:299:in `io'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis/client.rb:310:in `read'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis/client.rb:161:in `block in call'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis/client.rb:279:in `block (2 levels) in process'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis/client.rb:420:in `ensure_connected'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis/client.rb:269:in `block in process'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis/client.rb:356:in `logging'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis/client.rb:268:in `process'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis/client.rb:161:in `call'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/rack-mini-profiler-3.0.0/lib/mini_profiler/profiling_methods.rb:85:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis.rb:270:in `block in send_command'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis.rb:269:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis.rb:269:in `send_command'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis/commands/scripting.rb:110:in `_eval'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/redis-4.8.0/lib/redis/commands/scripting.rb:97:in `evalsha'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/message_bus-4.3.0/lib/message_bus/backends/redis.rb:463:in `cached_eval'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/message_bus-4.3.0/lib/message_bus/backends/redis.rb:150:in `publish'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/message_bus-4.3.0/lib/message_bus.rb:391:in `publish'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:161:in `publish'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:242:in `log'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:288:in `reload_unicorn'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:49: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.1.0/gems/railties-7.0.3.1/lib/rails/commands/runner/runner_command.rb:43:in `load'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.3.1/lib/rails/commands/runner/runner_command.rb:43:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/thor-1.2.1/lib/thor/command.rb:27:in `run'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.3.1/lib/rails/command/base.rb:87:in `perform'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.3.1/lib/rails/command.rb:48:in `invoke'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/railties-7.0.3.1/lib/rails/commands.rb:18:in `<main>'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/var/www/discourse/vendor/bundle/ruby/3.1.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
bin/rails:18:in `<main>'
2

Per quanto ne so, ho appena aggiornato con successo i miei due forum. Quindi, qualunque intoppo tu abbia incontrato, non è universale.

Il solito consiglio, quando l’aggiornamento basato sul browser fallisce, è eseguire un aggiornamento da riga di comando.

Questa è la versione su cui sono atterrato:

Installato
3.0.0.beta15
c2e18c41a3

2 Mi Piace
3

Sono sicuro che l’aggiornamento della CLI funzionerà, altrimenti questo forum sarebbe stato inondato di thread a quest’ora :smiley:

Ho semplicemente pensato di segnalare e attendere se qualcuno avesse bisogno di un log di qualche tipo prima di procedere con l’aggiornamento dalla CLI.

1 Mi Piace
4

Redis stesso tiene un registro da qualche parte? Deve essere stato in esecuzione a un certo punto, ma non ha risposto in tempo: è bloccato, lento o morto?

Modifica: ancora, FWIW, vedo che ho un file di log su

/var/discourse/shared/standalone/log/var-log/redis/current

ed è interamente ripetuto di segnalazioni come questa:

47:M 03 Jan 2023 18:50:11.090 * 100 changes in 300 seconds. Saving...
47:M 03 Jan 2023 18:50:11.091 * Background saving started by pid 31156
31156:C 03 Jan 2023 18:50:11.234 * DB saved on disk
31156:C 03 Jan 2023 18:50:11.236 * RDB: 1 MB of memory used by copy-on-write
47:M 03 Jan 2023 18:50:11.293 * Background saving terminated with success
47:M 03 Jan 2023 18:52:05.937 * 10000 changes in 60 seconds. Saving...
47:M 03 Jan 2023 18:52:05.940 * Background saving started by pid 31313
31313:C 03 Jan 2023 18:52:09.787 * DB saved on disk
31313:C 03 Jan 2023 18:52:09.791 * RDB: 3 MB of memory used by copy-on-write
47:M 03 Jan 2023 18:52:09.809 * Background saving terminated with success
47:M 03 Jan 2023 18:53:29.246 * 10000 changes in 60 seconds. Saving...
47:M 03 Jan 2023 18:53:29.248 * Background saving started by pid 31423
31423:C 03 Jan 2023 18:53:30.856 * DB saved on disk
31423:C 03 Jan 2023 18:53:30.857 * RDB: 2 MB of memory used by copy-on-write
47:M 03 Jan 2023 18:53:30.958 * Background saving terminated with success
47:M 03 Jan 2023 18:58:31.042 * 100 changes in 300 seconds. Saving...
47:M 03 Jan 2023 18:58:31.044 * Background saving started by pid 31753
31753:C 03 Jan 2023 18:58:31.212 * DB saved on disk
31753:C 03 Jan 2023 18:58:31.213 * RDB: 1 MB of memory used by copy-on-write
47:M 03 Jan 2023 18:58:31.245 * Background saving terminated with success