This update is failing for me, and right now, all 3 of my Discourse forums are down. The console window on the Upgrade screen is not populating with anything, but the rest of the UI suggests the upgrade is still in progress (but this has already taken a lot longer than any update I’ve ever done). Anyone else experiencing this? Any ideas for how I can get the upgrade to complete successfully?

Ahh, is that the issue with the ruby 3.0 error and web-push-3.0.0? The admin upgrade web UI should tell the user that rather than letting them click “upgrade all” and end up with a completely broken forum. Save a lot of users heart palpitations.

No idea; I personally don’t ever use the GUI for updates, I personally only ever do them from the command line. I didn’t see any errors that looked like that. But then also I would not have. Most of the time when you see a generic error message, if the specific scenario could was foreseen sufficiently for a specific error message, it would have instead been avoided. I guess it’s a good thing that the “help my GUI update failed” problem is so rare that most people don’t realize that the first thing to do is to just go do git pull; ./launcher rebuild app for the default deployment. It is almost always the answer here. But it is the general thing to do if the GUI update fails.

I’ve been using discourse for many years now. Like 7? Anyway, never had a web upgrade fail catastrophically before. It has failed of course, but the forum always came back to life because it rolled back and started up the old container. It isn’t a generic error, the ruby thing is pretty clear. web-push-3.0.0 requires ruby version >= 3.0, which is incompatible with the current version, 2.7.6 Docker Manager: FAILED TO UPGRADE I would be complaining pretty loudly about this if I paid for Discourse. Not because there’s a huge bug that killed our forum, bugs happen, but because it wasn’t fixed in at least the past 3 days. As is, just a bit of excitement at the end of the day.

From the perspective of the docker manager, that code as of when the version already running was written did not know that in the future this problem would happen. I hear that you are frustrated, but what you are asking for might not make sense technically. If you paid for Discourse, they would be managing this process and you’d never see it. :smiling_face:

Even if technically impossible to fix, you could send users emails to warn them to upgrade via CLI. Make some noise about it. Breaking forums with no rollback is bad. I thought Discourse also sold support for on-prem usage? Either way, I can’t complain too loudly as I’m not a paying customer, but geez, 3 days is not great.

I’m happy for you that this is the first time in seven years that you’ve had to fall back to to this, but: [תמונה] Wingtip: Breaking forums with no rollback is bad. I’m going to call that out as a mischaracterization. CDCK do actually recommend backups before updates as a best practice. I’ve seen many times here on meta the note that if the GUI update fails, fall back to rebuilding from the command line, as part of normal expectations for administering your own forum. They did not break forums with no rollback so your implication is false. I’m not going to sit here arguing for hours. I just think you aren’t being completely reasonable here.

Furthermore, upgrading a production server without running said upgrade through some form of staging environment is just asking for pain. It doesn’t have to be a full scale copy, a $5 VPS will suffice for most. If you want to avoid downtime and the need to turn to your backups it’s the cheapest insurance you can get.

I’ve just tested this out on a test DO instance that hasn’t been updated in yonks: [image] and as reported it errored out: Fetching gem metadata from https://rubygems.org/......... Fetching https://github.com/rails/sprockets web-push-3.0.0 requires ruby version >= 3.0, which is incompatible with the current version, 2.7.6 Docker Manager: FAILED TO UPGRADE # /var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:209:in `run' /var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:93:in `upgrade' /var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:19:in `block in ' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3.1/lib/active_support/fork_tracker.rb:20:in `block in fork' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3.1/lib/active_support/fork_tracker.rb:18:in `fork' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-7.0.3.1/lib/active_support/fork_tracker.rb:18:in `fork' /var/www/discourse/plugins/docker_manager/scripts/docker_manager_upgrade.rb:6:in ` ' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3.1/lib/rails/commands/runner/runner_command.rb:43:in `load' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3.1/lib/rails/commands/runner/runner_command.rb:43:in `perform' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.2.1/lib/thor/command.rb:27:in `run' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3.1/lib/rails/command/base.rb:87:in `perform' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3.1/lib/rails/command.rb:48:in `invoke' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3.1/lib/rails/commands.rb:18:in ` ' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.13.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.13.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require' bin/rails:18:in ` ' Spinning up 3 Unicorn worker(s) that were stopped initially and the upgrade page now shows: [image] and the main site 500s. In /logs I see this error: NoMethodError (undefined method `navigation_menu' for # ) lib/wizard/builder.rb:98:in `block in build' lib/wizard.rb:25:in `append_step' lib/wizard/builder.rb:61:in `build' lib/wizard.rb:110:in `requires_completion?' lib/wizard.rb:117:in `user_requires_completion?' app/serializers/site_serializer.rb:171:in `include_wizard_required?' … @pearsonified @mcdanlj Can you paste what errors you were getting? I don’t know if we can do anything now to prevent this for future users, but we’ll look into it. In the meanwhile, did the following steps help? [image]

Gonna run the command-line upgrades this morning and see how that goes. Forums have been down 18 hours now :pensive_face:

בעיות בשדרוג עצמי ל-3.x: לא ניתן לחזור לאחור

תמיכה התקנה

mcdanlj (Michael K Johnson) 25 בינואר,‏ 2023,‏ 8:51pm 2

@pearsonified because this includes an update to the Rails component, this is one of those releases that needs an update from the command line.

נושא		תגובות	צפיות
Failed upgrade from 2.9.0.beta14 to 3.1.0.beta Self-hosting	10	1381	25 בינואר,‏ 2023
Discourse broken after failed upgrade Product Support install	4	484	2 בנובמבר,‏ 2024
Error when upgrading and would like to solve or reset Self-hosting	8	1528	2 בספטמבר,‏ 2022
Runtime error during upgrade to v3.0.3 Self-hosting	16	1540	19 באפריל,‏ 2023
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	16	2494	26 בנובמבר,‏ 2021

בעיות בשדרוג עצמי ל-3.x: לא ניתן לחזור לאחור

נושאים קשורים