# I keep getting errors when updating **URL:** https://meta.discourse.org/t/i-keep-getting-errors-when-updating/373634 **Category:** Support **Created:** [July 9, 2025, 8:40pm UTC](https://meta.discourse.org/t/i-keep-getting-errors-when-updating/373634 "2025-07-09T20:40:53Z") **Posts on this page:** 1 **Showing post:** 1
### Author: ![alltiagocom](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/alltiagocom/32/492709_2.png) [@alltiagocom](https://meta.discourse.org/u/alltiagocom) #### Post date: [July 9, 2025, 8:40pm UTC](https://meta.discourse.org/t/i-keep-getting-errors-when-updating/373634/1 "2025-07-09T20:40:53Z")
No matter how many times I try to update, I always get `Sorry, there was an error updating Discourse. Please check the logs below.` when updating via the browser. I always have to rely on Terminal and that isn’t good, because then I will always have to have my forum down for like 30 minutes. If anyone can help me here, that would be appreciated. Errors: > **Summary** > > ```plaintext > ******************************************************** > ***Please be patient, next steps might take a while*** > ******************************************************** > Cycling Unicorn, to free up memory > Restarting unicorn pid: 603 > 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....................... > 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............................... > $ cd /var/www/discourse && git reset --hard HEAD@{upstream} > HEAD is now at fe1b1edba FIX: removes + from RTE toggle tooltip (#33542) > $ bundle install --retry 3 --jobs 4 > Bundle complete! 143 Gemfile dependencies, 190 gems now installed. > Gems in the groups 'test' and 'development' were not installed. > Bundled gems are installed into `./vendor/bundle` > 3 installed gems you directly depend on are looking for funding. > Run `bundle fund` for details > $ if [-f yarn.lock]; then yarn install; else CI=1 pnpm install; fi > Scope: all 16 workspace projects > Lockfile is up to date, resolution step is skipped > Already up to date > > Done in 9.1s using pnpm v9.15.6 > $ LOAD_PLUGINS=0 bundle exec rake plugin:pull_compatible_all > discourse-adplugin is already at latest compatible version > discourse-categories-suppressed is already at latest compatible version > discourse-doc-categories is already at latest compatible version > Invalid version list in /var/www/discourse/plugins/discourse-landing-pages > discourse-landing-pages is already at latest compatible version > discourse-solved is already at latest compatible version > 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 > Updating themes with concurrency: 10 > [db:default] 'New Topic Header Button' - checking... > [db:default] 'New Topic Header Button' - up to date > [db:default] 'Category Banners' - checking... > [db:default] 'Category Banners' - up to date > [db:default] 'Clickable Topic' - checking... > [db:default] 'Clickable Topic' - up to date > [db:default] 'Tag Banners' - checking... > [db:default] 'Tag Banners' - up to date > [db:default] 'Breadcrumb Links' - checking... > [db:default] 'Breadcrumb Links' - up to date > [db:default] 'Welcome Link Banner' - checking... > [db:default] 'Welcome Link Banner' - up to date > [db:default] 'Tag Icons' - checking... > [db:default] 'Tag Icons' - up to date > [db:default] 'Social Share' - checking... > [db:default] 'Social Share' - up to date > [db:default] 'Navigation Menu Display Control' - checking... > [db:default] 'Navigation Menu Display Control' - up to date > [db:default] 'DiscoTOC' - checking... > Node.js heap_size_limit is less than 2048MB. Setting --max-old-space-size=2048 and CHEAP_SOURCE_MAPS=1 > Existing build is not reusable. > - Existing: {"ember_env"=>"production", "core_tree_hash"=>"c71c1ad482ff7f24c3ad3a76d5a521861f29e1fb"} > - Current: {"ember_env"=>"production", "core_tree_hash"=>"d026d5621e9421eaf67123aab7361a44f0fa9c31"} > Running full core build... > Building > Environment: production > The setting 'staticAddonTrees' will default to true in the next version of Embroider and can't be turned off. To prepare for this you should set 'staticAddonTrees: true' in your Embroider config. > The setting 'staticAddonTestSupportTrees' will default to true in the next version of Embroider and can't be turned off. To prepare for this you should set 'staticAddonTestSupportTrees: true' in your Embroider config. > building... > ...[ConfigLoader] > ...[Babel: @embroider/macros > applyPatches] > ...[Babel: pretty-text > applyPatches] > ...[Babel: @ember/legacy-built-in-components > applyPatches] > ...[Babel: ember-source > applyPatches] > [BABEL] Note: The code generator has deoptimised the styling of /var/www/discourse/app/assets/javascripts/discourse/ember/ember-template-compiler.js as it exceeds the max of 500KB. > [BABEL] Note: The code generator has deoptimised the styling of /var/www/discourse/app/assets/javascripts/discourse/ember/ember.js as it exceeds the max of 500KB. > ...[Babel: @glimmer/component > applyPatches] > ...[Babel: @ember/render-modifiers > applyPatches] > ...[Babel: dialog-holder > applyPatches] > ...[Babel: ember-this-fallback > applyPatches] > ...[Babel: ember-buffered-proxy > applyPatches] > ...[Babel: ember-cache-primitive-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] > undefined > ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL Command was killed with SIGKILL (Forced termination): ember build -prod > /var/www/discourse/script/assemble_ember_build.rb:103:in `system': Command failed with exit 1: pnpm (RuntimeError) > from /var/www/discourse/script/assemble_ember_build.rb:103:in `
' > Docker Manager: FAILED TO UPGRADE > # > /var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:211:in `run' > /var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:112: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.3.0/gems/railties-7.2.2.1/lib/rails/commands/runner/runner_command.rb:44:in `load' > /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/commands/runner/runner_command.rb:44:in `block in perform' > /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/execution_wrapper.rb:91:in `wrap' > /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/commands/runner/runner_command.rb:70:in `conditional_executor' > /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/commands/runner/runner_command.rb:43: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.2.2.1/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.2.2.1/lib/rails/command/base.rb:73:in `perform' > /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/command.rb:71:in `block in invoke' > /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/command.rb:149:in `with_argv' > /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/command.rb:69:in `invoke' > /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/commands.rb:18:in `
' > /usr/local/lib/ruby/3.3.0/bundled_gems.rb:69:in `require' > /usr/local/lib/ruby/3.3.0/bundled_gems.rb:69:in `block (2 levels) in replace_require' > /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require' > bin/rails:18:in `
' > Spinning up 1 Unicorn worker(s) that were stopped initially > > ``` --- _[View the full topic](https://meta.discourse.org/t/i-keep-getting-errors-when-updating/373634)._