# Failed upgrade from 2.9.0.beta14 to 3.1.0.beta **URL:** \ **Category:** Self-hosting\ **Created:** [January 22, 2023, 7:16pm UTC](https://meta.discourse.org/t/failed-upgrade-from-2-9-0-beta14-to-3-1-0-beta/252551 "2023-01-22T19:16:24Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![xyzzy](https://avatars.discourse-cdn.com/v4/letter/x/e36b37/32.png) [@xyzzy](https://meta.discourse.org/u/xyzzy)\ **Post date:** [January 22, 2023, 7:16pm UTC](https://meta.discourse.org/t/failed-upgrade-from-2-9-0-beta14-to-3-1-0-beta/252551/1 "2023-01-22T19:16:24Z")
I upgrade every month, always on a few development systems first, then production. During this month’s cycle, the upgrade failed on the 1st development system. docker\_manager upgraded fine but the discourse upgrade failed with: `Sorry, there was an error upgrading Discourse. Please check the logs below.` The Discourse app is completely down (it’s displaying the “Oops” error 500 page). Here’s what the on-screen log contains: ```plaintext ******************************************************** ***Please be patient, next steps might take a while*** ******************************************************** Cycling Unicorn, to free up memory Restarting unicorn pid: 50 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........... Stopping 7 Unicorn worker(s), to free up memory Stopping job queue to reclaim memory, master pid is 4069 $ cd /var/www/discourse && git fetch --tags --force && git reset --hard HEAD@{upstream} From https://github.com/discourse/discourse t [tag update] latest-release -> latest-release * [new tag] v2.8.14 -> v2.8.14 * [new tag] v3.0.0 -> v3.0.0 HEAD is now at 666536cbd1 DEV: Prefer \A and \z over ^ and $ in regexes (#19936) $ bundle install --deployment --jobs 4 --without test development [DEPRECATED] The `--deployment` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local deployment 'true'`, and stop using this flag [DEPRECATED] The `--without` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local without 'test development'`, and stop using this flag Bundler 2.3.13 is running, but your lockfile was generated with 2.4.1. Installing Bundler 2.4.1 and restarting using that version. Fetching gem metadata from https://rubygems.org/. Fetching bundler 2.4.1 Installing bundler 2.4.1 [DEPRECATED] The `--deployment` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local deployment 'true'`, and stop using this flag [DEPRECATED] The `--without` flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use `bundle config set --local without 'test development'`, and stop using this flag 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.15.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.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require' bin/rails:18:in `
' Spinning up 7 Unicorn worker(s) that were stopped initially ``` I’ve never had an upgrade error before so I’m unclear what to do next. And if this had happened in production, what would I do? --- _[View the full topic](https://meta.discourse.org/t/failed-upgrade-from-2-9-0-beta14-to-3-1-0-beta/252551)._