Docker Manager: FAILED TO UPGRADE # /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:101:in `upgrade' /var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:19:in `block in ' /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 ` ' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8.1/lib/rails/commands/runner/runner_command.rb:43:in `load' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8.1/lib/rails/commands/runner/runner_command.rb:43:in `perform' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/thor-1.3.1/lib/thor/command.rb:28:in `run' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/thor-1.3.1/lib/thor/invocation.rb:127:in `invoke_command' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/thor-1.3.1/lib/thor.rb:527:in `dispatch' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8.1/lib/rails/command/base.rb:87:in `perform' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8.1/lib/rails/command.rb:48:in `invoke' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.8.1/lib/rails/commands.rb:18:in ` ' :37:in `require' :37:in `require' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require' bin/rails:18:in ` ' Spinning up 3 Unicorn worker(s) that were stopped initially i got this error, how do i fix it?

Are you doing a .launcher rebuild app from the command line, or updating from the UI? If the latter, could you try the former?

I just update the discorse from settings :frowning: not from the command line

I think a manual rebuild should sort you out. :crossed_fingers: [immagine] Manually update Discourse and Docker image to latest Self-Hosting bookmark This guide provides step-by-step instructions for manually updating Discourse, the Docker container, and the Ubuntu operating system on a self-hosted setup. person_raising_hand Required user level: System Administrator warning SSH access to the server. If you self-host Discourse, you occasionally need to run a manual update via the command line to get the latest security releases and newest libraries. These updates are not picked up in admin/upgrade, which is why you’ll occa…

It looks like it’s not possible to do this upgrade from the UI and that Discourse_docker should not attempt to do an upgrade. I’ve at two sites that broke doing the upgrade and this is at least the second one I’ve seen here since the latest release.

I think David has added a message now: [immagine] 3.3.0.beta2-dev update error Self-hosting Thanks for the reports! A command line rebuild is indeed the best solution. I’ve prepared this fix which will cause a message to be shown to people before they hit ‘update’ in the UI. Edit: now merged

Errore 500 come risolvere?

Assistenza prodotto Installazione

JammyDodger 16 Maggio 2024, 1:23pm 4

Penso che una ricostruzione manuale dovrebbe risolverti.

Argomento		Risposte	Visualizzazioni
:cn: 500 error when upgrading Discourse \| Discourse 升级时候 500 错误 Sysadmins chinese-translation	2	433	Maggio 19, 2024
Failed Upgrade Discourse and Plugins Self-hosting	17	1412	Febbraio 10, 2022
500 error on /admin/upgrade Product Support	3	215	Gennaio 8, 2026
Link to upgrade shows 500 error Bug	6	1191	Ottobre 2, 2017
Error when upgrading and would like to solve or reset Self-hosting	8	1511	Settembre 2, 2022

Errore 500 come risolvere?

Argomenti correlati