For standard install site have this error log for most recent upgrade: ******************************************************** *** Please be patient, next steps might take a while *** ******************************************************** Cycling Unicorn, to free up memory Restarting unicorn pid: 545 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........... 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...................... Waiting for Unicorn to reload....................... Using libv8-node 18.16.0.0 (x86_64-linux) Using method_source 1.0.0 Using thor 1.3.0 Using zeitwerk 2.6.12 Using railties 7.0.7 Using request_store 1.5.1 Using lograge 0.14.0 Using logstash-event 1.2.02 Using logstash-logger 0.26.1 Using logster 2.13.1 Using lru_redux 1.1.0 Using lz4-ruby 0.3.3 Using maxminddb 0.1.22 Using memory_profiler 1.0.1 Using message_bus 4.3.8 Using mini_racer 0.8.0 Using redis 4.8.1 Using sidekiq 6.5.12 Using mini_scheduler 0.16.0 Using mini_sql 1.5.0 Using mini_suffix 0.3.3 Using multi_json 1.15.0 Using multi_xml 0.6.0 Using mustache 1.1.1 Using uri 0.13.0 Using net-http 0.4.0 Using nio4r 2.7.0 Using version_gem 1.1.3 Using oauth-tty 1.0.5 Using snaky_hash 2.0.1 Using oauth 1.1.0 Using oauth2 1.4.11 Using oj 3.16.3 Using omniauth 1.9.2 Using omniauth-oauth2 1.7.3 Using omniauth-facebook 9.0.0 Using omniauth-github 1.4.0 Using omniauth-google-oauth2 0.8.2 Using omniauth-oauth 1.2.0 Using omniauth-twitter 1.4.0 Using optimist 3.1.0 Using pg 1.5.4 Using pry 0.14.2 Using pry-byebug 3.10.1 Using pry-rails 0.3.9 Using puma 6.4.0 Using rack-mini-profiler 3.3.0 Using rack-protection 3.1.0 Using rails_failover 2.0.1 Using rails_multisite 5.0.0 Using raindrops 0.20.1 Using rbtrace 0.5.1 Using rchardet 1.8.0 Using redis-namespace 1.11.0 Using rexml 3.2.6 Using rinku 2.0.6 Using rotp 6.3.0 Using rqrcode_core 1.2.0 Using rqrcode 2.2.0 Using rss 0.3.0 Using rtlcss 0.2.1 Using ruby-readability 0.7.0 Using rubyzip 2.3.2 Using sanitize 6.1.0 Using sass-embedded 1.69.5 (x86_64-linux-gnu) Using sassc-embedded 1.68.6 Using sprockets 3.7.2 from https://github.com/rails/sprockets (at 3.x@f4d3dae) Using sprockets-rails 3.4.2 Using sshkey 3.0.0 Using stackprof 0.2.25 Using tzinfo-data 1.2023.4 Using uglifier 4.2.0 Using unicorn 6.1.0 Using web-push 3.0.1 Bundle complete! 138 Gemfile dependencies, 171 gems now installed. Gems in the groups 'development' and 'test' were not installed. Bundled gems are installed into `./vendor/bundle` 1 installed gem you directly depend on is looking for funding. Run `bundle fund` for details $ yarn install yarn install v1.22.19 [1/5] Validating package.json... [2/5] Resolving packages... success Already up-to-date. $ yarn --cwd app/assets/javascripts $(node -e 'const argv = JSON.parse(process.env.npm_config_argv).original; const passthrough = [`--frozen-lockfile`, `-s`].filter(arg => argv.includes(arg)); console.log(passthrough.join(` `));') yarn install v1.22.19 [1/4] Resolving packages... warning Resolution field "unset-value@2.0.1" is incompatible with requested version "unset-value@^1.0.0" success Already up-to-date. $ ./run-patch-package patch-package 8.0.0 Applying patches... babel-plugin-debug-macros@0.3.4 ✔ content-tag@1.2.2 ✔ ember-cli@5.0.0 ✔ ember-this-fallback@0.4.0 (1 deprecation-name) ✔ ember-this-fallback@0.4.0 (2 themes) ✔ virtual-dom@2.1.1 ✔ Done in 4.79s. Done in 7.25s. $ LOAD_PLUGINS=0 bundle exec rake plugin:pull_compatible_all docker_manager is already at latest compatible version $ SKIP_POST_DEPLOYMENT_MIGRATIONS=1 bundle exec rake multisite:migrate Multisite migrator is running using 1 threads Migrating default Seeding default *** Bundling assets. This will take a while *** $ bundle exec rake themes:update assets:precompile Checking 'Air Theme' for 'default'... updating from b9d44745 to 85dc24d6 Checking 'Modern Category + Group Boxes' for 'default'... up to date Checking 'Discourse Clickable Topic' for 'default'... up to date Checking 'discourse-search-banner' for 'default'... updating from 934e0d35 to 6ba0e9d0 Node.js heap_size_limit (488.25) is less than 2048MB. Setting --max-old-space-size=2048. yarn run v1.22.19 $ /var/www/discourse/app/assets/javascripts/node_modules/.bin/ember build Building Environment: development WARNING: ember-test-selectors: You are using an unsupported ember-cli-babel version. data-test properties are not automatically stripped from your JS code. building... ...[ConfigLoader] ...[Babel: @embroider/macros > applyPatches] ...[Babel: discourse-widget-hbs > applyPatches] ...[Babel: ember-source > applyPatches] ...[ember.js] ...[Babel: discourse-common > applyPatches] ...[Babel: truth-helpers > applyPatches] ...[Babel: ember-tracked-storage-polyfill > applyPatches] ...[Babel: @ember/legacy-built-in-components > applyPatches] ...[Babel: @ember/render-modifiers > applyPatches] ...[Babel: @ember/test-helpers > applyPatches] ...[Babel: @ember/test-waiters > applyPatches] ...[Babel: @embroider/util > applyPatches] ...[Babel: @glimmer/component > applyPatches] ...[Babel: dialog-holder > applyPatches] ...[Babel: ember-this-fallback > applyPatches] ...[Babel: ember-buffered-proxy > applyPatches] ...[Babel: ember-cached-decorator-polyfill > applyPatches] ...[Babel: ember-exam > applyPatches] ...[Babel: ember-functions-as-helper-polyfill > applyPatches] ...[Babel: ember-load-initializers > applyPatches] ...[Babel: ember-on-resize-modifier > applyPatches] ...[Babel: ember-resize-observer-service > applyPatches] ...[Babel: ember-router-service-refresh-polyfill > applyPatches] ...[Babel: float-kit > applyPatches] ...[Babel: select-kit > applyPatches] ...[@embroider/compat/app] ...[@embroider/webpack] ...[@embroider/webpack] ...[@embroider/webpack] ...[@embroider/webpack] ...[@embroider/webpack] ...[@embroider/webpack] ...[@embroider/webpack] ...[@embroider/webpack] ...[@embroider/webpack] ...[@embroider/webpack] ...[@embroider/webpack] ...[@embroider/webpack] ...[@embroider/webpack] ...[@embroider/webpack] ...[@embroider/webpack] ...[@embroider/webpack] ...[@embroider/webpack] Killed error Command failed with exit code 137. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. 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:111: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.7/lib/rails/commands/runner/runner_command.rb:43:in `load' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.7/lib/rails/commands/runner/runner_command.rb:43:in `perform' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/thor-1.3.0/lib/thor/command.rb:28:in `run' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/thor-1.3.0/lib/thor/invocation.rb:127:in `invoke_command' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/thor-1.3.0/lib/thor.rb:527:in `dispatch' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.7/lib/rails/command/base.rb:87:in `perform' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.7/lib/rails/command.rb:48:in `invoke' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/railties-7.0.7/lib/rails/commands.rb:18:in ` ' :37:in `require' :37:in `require' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/bootsnap-1.17.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require' bin/rails:18:in ` ' Spinning up 1 Unicorn worker(s) that were stopped initially Seems to still be working to process upgrade not sure if this is any kind of a serious problem or what can be done for this. [error log]

[image] anon36555649: exit code 137 Out of memory. You’ll need to add swap or ram. But also you can try again and it might work. If you’re updating from the UX you should try a command line rebuild.

I think you may benefit from reading some more topics on the subject. If you have a search of the #documentation, or just a search in general, I think you’ll find plenty of information that should help fill in the gaps in your knowledge. There is a substantial amount of advice that covers the basics that you can learn from. :+1:

[image] Jay Pfaffman: command line rebuild Missed that you wrote rebuild can rebuild the app. Here is the official guide: [image] 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…

Because running the website (albeit with fewer Unicorns) + performing a build at the same time is costly in memory? I tried this out on my server (3 VCPU, 4GB): Online: 2.21 before upgrade → 1.7 as it frees up memory → 3.5 peak during build (GBs) Swap also went up ~200MB to peak ~800MB Command line (not apples to apples as just after the above) 1.7 before upgrade → drops to ~250MB! → climbs and climbs to peak 3.25 during assets compilation, but generally much lower. Swap usage was very low during almost the entire process. Caveat: all figures observed in htop so may be inaccurate, probably best to graph it. I was surprised how “peaky” offline rebuilds were. Assets precompile definitely uses a lot of memory - perhaps more the more VCPUs you have as it might do some of that in parallel? I was also suprised how little difference the peak was in my case, though swap usage was significantly lower and generally, memory use was much lower for an offline rebuild, remaining in the 100’s of MB during 95% of the process, whereas an online upgrade was minimum 1.7GB.

[image] Robert: Because running the website (albeit with fewer Unicorns) + performing a build at the same time is costly in memory? That seems correct, no need for a question mark there! So rebuilding the app then automatically updates to most recent version it seems? [Screen Shot 2024-02-01 at 4.39.44 PM] Is there a supported or non-supported way to keep previous versions of discourse running, or do new installs for previous versions?

No, but you can slow things down by changing to stable. Unfortunately you just missed the boat this time as you can’t go backwards.

Ok, may want to change to that stable setting for only stable tested updates not the developer/beta ones. Looking to figure out how to do that.

[image] anon36555649: only stable tested updates not the developer/beta ones Did you read about the meaning of those? [image] Understanding Discourse release channels Site Management bookmark This guide explains the different types of Discourse releases and how different channels are used for updates. person_raising_hand Required user level: All users Release channels Discourse has four primary release channels, each serving a different purpose: main, latest, release, and esr. The default channel used when installing a production version of Discourse is latest. Since November 2025, Discourse uses a date-based versioning scheme: YYYY.MM.PATCH (e.g., v2026.2.0). On … [image] From Discourse 3.2: adding -dev suffix to beta versions under active development megaphoneAnnouncements On tests-passed, starting with 3.2.0.beta1-dev, Discourse core version numbers will include a -dev suffix to indicate that they’re not the final ‘release’ versions of a beta. This suffix doesn’t appear in the UI, so this is a technicality which will have no impact on the vast majority of people. For the technical details, see below: In the beta series for Discourse 3.1 and below, our versioning strategy was to ‘release’ a beta, and then leave the version number in tests-passed exactly the sam…

Have read through those now, haven’t yet figured out how to change update settings for stable vs. main / beta / or tests-passed. Edit: Could be the answer is there isn’t a setting for this, maybe dev updates can only be done manually or something? Am just guessing don’t know.

Side note: During rebuild have notice that: 110:M 11 Feb 2024 04:26:05.828 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. Not sure how to do this, how is this done does anyone know?: add 'vm.overcommit_memory = 1' to /etc/sysctl.conf

Problem with Upgrade [error 137]

Product Support Self-hosting

Moin February 2, 2024, 12:59am 21

Did you read about the meaning of those?

Topic		Replies	Views
I keep getting errors when updating Product Support	26	744	July 16, 2025
2.6.0 beta 3 update failed on disk and/or memory space Self-hosting server-resources	28	3075	September 26, 2020
Failed to upgrade discourse instance to Feb 15 2022 Self-hosting server-resources	29	3339	February 16, 2022
Error while updating through launcher rebuild Self-hosting	2	677	April 16, 2024
Upgrade failed, "FAILED TO BOOTSTRAP", error 137 Self-hosting server-resources	5	1171	October 12, 2022

Problem with Upgrade [error 137]

Related topics