从 2.9.0.beta14 升级到 3.0.0.beta15 失败

[Crius]

在搜索“upgrade failed”时，没有找到提及此版本升级的主题。

我收到了通知，这是一个简单的实例，除了管理员之外没有任何用户活动。我使用此安装来测试功能，然后再将其推广到实际的生产环境。

单击管理面板中的升级按钮，然后单击开始升级，会返回此错误：

********************************************************
*** 请耐心等待，后续步骤可能需要一段时间 ***
********************************************************
正在重启 Unicorn，以释放内存
正在重启 unicorn pid: 548
等待 Unicorn 重新加载。
等待 Unicorn 重新加载..
等待 Unicorn 重新加载...
等待 Unicorn 重新加载....
等待 Unicorn 重新加载.....
等待 Unicorn 重新加载......
等待 Unicorn 重新加载.......
等待 Unicorn 重新加载........
等待 Unicorn 重新加载.........
等待 Unicorn 重新加载..........
等待 Unicorn 重新加载..........
Docker Manager: 升级失败
#<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>'

[Ed_S]

FWIW 我刚刚成功升级了我的两个论坛。所以无论你遇到什么障碍，都不是普遍存在的。

通常的建议是，当基于浏览器的更新失败时，运行命令行更新。

这是我最终使用的版本：

已安装
3.0.0.beta15
c2e18c41a3

[Crius]

我确信 CLI 更新会奏效，否则此时论坛上早就充斥着各种帖子了
我只是想报告一下，看看是否有人需要某种日志，然后再通过 CLI 进行更新。

[Ed_S]

Redis 本身有日志记录在某处吗？它肯定在某个时候运行过，但没有及时响应——是卡住了、变慢了还是死掉了？

编辑：再说一次，就我所知，我在以下位置找到了一个日志文件：

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

它完全是类似这样的报告的重复：

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