更新后出现错误(S3 备份插件)」}

不久前,我在更新时遇到一个错误,所以我尝试用 git pull 和重建等方法来修复它。
错误仍然存在,用户也一直在报告错误等。这是最近尝试更新 Docker 时出现的错误:

Compressing: vendor.fc515a92f838bfb06405ac3186d67213-d190f217c498848c25a4048fe73ad56cbd28decf7b7eddf1b7ea34d79ee1ee6d.js
pnpm terser '/var/www/discourse/public/assets/_vendor.fc515a92f838bfb06405ac3186d67213-d190f217c498848c25a4048fe73ad56cbd28decf7b7eddf1b7ea34d79ee1ee6d.js' -m -c -o '/var/www/discourse/public/assets/vendor.fc515a92f838bfb06405ac3186d67213-d190f217c498848c25a4048fe73ad56cbd28decf7b7eddf1b7ea34d79ee1ee6d.js' --source-map "base='/var/www/discourse/public/assets',root='/assets',url='vendor.fc515a92f838bfb06405ac3186d67213-d190f217c498848c25a4048fe73ad56cbd28decf7b7eddf1b7ea34d79ee1ee6d.js.map',includeSources=true"
rake aborted!
Errno::ENOENT: No such file or directory @ rb_file_s_size - /var/www/discourse/public/assets/vendor.fc515a92f838bfb06405ac3186d67213-d190f217c498848c25a4048fe73ad56cbd28decf7b7eddf1b7ea34d79ee1ee6d.js (Errno::ENOENT)
/var/www/discourse/lib/tasks/assets.rake:297:in `size'
/var/www/discourse/lib/tasks/assets.rake:297:in `block (6 levels) in <main>'
/var/www/discourse/lib/tasks/assets.rake:250:in `log_task_duration'
/var/www/discourse/lib/tasks/assets.rake:289:in `block (5 levels) in <main>'
/var/www/discourse/lib/tasks/assets.rake:240:in `block in concurrent?'
/var/www/discourse/lib/tasks/assets.rake:288:in `block (4 levels) in <main>'
/var/www/discourse/lib/tasks/assets.rake:271:in `each'
/var/www/discourse/lib/tasks/assets.rake:271:in `block (3 levels) in <main>'
/var/www/discourse/lib/tasks/assets.rake:240:in `concurrent?'
/var/www/discourse/lib/tasks/assets.rake:267:in `block (2 levels) in <main>'
/var/www/discourse/lib/tasks/assets.rake:250:in `log_task_duration'
/var/www/discourse/lib/tasks/assets.rake:266:in `block in <main>'
/var/www/discourse/lib/tasks/assets.rake:332:in `block in <main>'
Tasks: TOP => assets:precompile:compress_js
(See full trace by running task with --trace)
Docker Manager: FAILED TO UPGRADE
#<RuntimeError: RuntimeError>
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:210:in `run'
/var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:111: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>'

错误日志中也有关于同一个丢失文件的条目等。
有什么好的方法可以解决这个问题吗?

您有自定义插件吗?

1 个赞

所有插件均归功于 Discourse

备份上传到 s3 已弃用。这可能会有问题。

由于它是唯一一个我无法通过界面禁用的选项,并且我在设置中找不到它,我需要通过终端删除它吗?

是的。您可以在 yml 文件中注释掉它,然后重新构建。

已完成,并进行了另一次重建 - 没有错误。
已要求社区在出现任何问题时告知我,但看起来问题已解决。
谢谢!

1 个赞

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.