Hi everyone, I’m having trouble updating my Discourse forum through the admin panel, and I could use some help figuring out what’s going wrong. When I try to update, I get an error message, and it stops the whole process. Here’s what’s happening: I’m using the Update Discourse from admin panel to do the update. When updating Discourse from admin panel False False False is displayed numerous times then an error saying updating discourse failed with this error. false - ./node_modules/.bin - /var/www/discourse/node_modules/.bin - /var/www/discourse/vendor/bundle/ruby/3.3.0/bin - /usr/local/sbin - /usr/local/bin - /usr/sbin - /usr/bin - /sbin - /bin PLATFORM: linux x64 FREEMEM: 61129658368 TOTALMEM: 67272630272 UPTIME: 30579.58 LOADAVG: 1.15,0.42,0.16 CPUS: - Intel(R) Xeon(R) E-2276G CPU @ 3.80GHz - 4300 - Intel(R) Xeon(R) E-2276G CPU @ 3.80GHz - 3223 - Intel(R) Xeon(R) E-2276G CPU @ 3.80GHz - 2548 - Intel(R) Xeon(R) E-2276G CPU @ 3.80GHz - 4039 - Intel(R) Xeon(R) E-2276G CPU @ 3.80GHz - 1358 - Intel(R) Xeon(R) E-2276G CPU @ 3.80GHz - 1200 - Intel(R) Xeon(R) E-2276G CPU @ 3.80GHz - 1200 - Intel(R) Xeon(R) E-2276G CPU @ 3.80GHz - 1200 - Intel(R) Xeon(R) E-2276G CPU @ 3.80GHz - 3954 - Intel(R) Xeon(R) E-2276G CPU @ 3.80GHz - 1200 - Intel(R) Xeon(R) E-2276G CPU @ 3.80GHz - 1199 - Intel(R) Xeon(R) E-2276G CPU @ 3.80GHz - 1676 ENDIANNESS: LE VERSIONS: - acorn: 8.14.0 - ada: 2.9.2 - amaro: 0.3.0 - ares: 1.34.4 - brotli: 1.1.0 - cjs_module_lexer: 1.4.1 - cldr: 46.0 - icu: 76.1 - llhttp: 9.2.1 - modules: 127 - napi: 10 - nbytes: 0.1.1 - ncrypto: 0.0.1 - nghttp2: 1.64.0 - nghttp3: 1.6.0 - ngtcp2: 1.10.0 - node: 22.14.0 - openssl: 3.0.15+quic - simdjson: 3.10.1 - simdutf: 6.0.3 - sqlite: 3.47.2 - tz: 2024b - undici: 6.21.1 - unicode: 16.0 - uv: 1.49.2 - uvwasi: 0.0.21 - v8: 12.4.254.21-node.22 - zlib: 1.3.0.1-motley-82a5fec ERROR Summary: - broccoliBuilderErrorStack: Error: assets/chunk.cbb4d6362a2090db10ec.d41d8cd9.js from Terser plugin failed to handle: failed printing to stdout: Resource temporarily unavailable (os error 11) Error: failed to handle: failed printing to stdout: Resource temporarily unavailable (os error 11) at TerserPlugin.buildError (/var/www/discourse/node_modules/.pnpm/terser-webpack-plugin@5.3.11_@swc+core@1.11.1_esbuild@0.25.0_webpack@5.98.0_@swc+core@1.11.1_esbuild@0.25.0_/node_modules/terser-webpack-plugin/dist/index.js:266:20) at /var/www/discourse/node_modules/.pnpm/terser-webpack-plugin@5.3.11_@swc+core@1.11.1_esbuild@0.25.0_webpack@5.98.0_@swc+core@1.11.1_esbuild@0.25.0_/node_modules/terser-webpack-plugin/dist/index.js:455:26 - code: [undefined] - codeFrame: assets/chunk.cbb4d6362a2090db10ec.d41d8cd9.js from Terser plugin failed to handle: failed printing to stdout: Resource temporarily unavailable (os error 11) Error: failed to handle: failed printing to stdout: Resource temporarily unavailable (os error 11) - errorMessage: assets/chunk.cbb4d6362a2090db10ec.d41d8cd9.js: assets/chunk.cbb4d6362a2090db10ec.d41d8cd9.js from Terser plugin failed to handle: failed printing to stdout: Resource temporarily unavailable (os error 11) Error: failed to handle: failed printing to stdout: Resource temporarily unavailable (os error 11) at PackagerRunner (@embroider/webpack) - errorType: Build Error - location: - column: [undefined] - file: assets/chunk.cbb4d6362a2090db10ec.d41d8cd9.js - line: [null] - treeDir: [undefined] - message: assets/chunk.cbb4d6362a2090db10ec.d41d8cd9.js: assets/chunk.cbb4d6362a2090db10ec.d41d8cd9.js from Terser plugin failed to handle: failed printing to stdout: Resource temporarily unavailable (os error 11) Error: failed to handle: failed printing to stdout: Resource temporarily unavailable (os error 11) at PackagerRunner (@embroider/webpack) - name: Error - nodeAnnotation: @embroider/webpack - nodeName: PackagerRunner - originalErrorMessage: assets/chunk.cbb4d6362a2090db10ec.d41d8cd9.js from Terser plugin failed to handle: failed printing to stdout: Resource temporarily unavailable (os error 11) Error: failed to handle: failed printing to stdout: Resource temporarily unavailable (os error 11) - stack: Error: assets/chunk.cbb4d6362a2090db10ec.d41d8cd9.js from Terser plugin failed to handle: failed printing to stdout: Resource temporarily unavailable (os error 11) Error: failed to handle: failed printing to stdout: Resource temporarily unavailable (os error 11) at TerserPlugin.buildError (/var/www/discourse/node_modules/.pnpm/terser-webpack-plugin@5.3.11_@swc+core@1.11.1_esbuild@0.25.0_webpack@5.98.0_@swc+core@1.11.1_esbuild@0.25.0_/node_modules/terser-webpack-plugin/dist/index.js:266:20) at /var/www/discourse/node_modules/.pnpm/terser-webpack-plugin@5.3.11_@swc+core@1.11.1_esbuild@0.25.0_webpack@5.98.0_@swc+core@1.11.1_esbuild@0.25.0_/node_modules/terser-webpack-plugin/dist/index.js:455:26 ================================================================================= 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.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in require’ bin/rails:18:in `’ Spinning up 7 Unicorn worker(s) that were stopped initially My setup: Running on Linux (x64 version). Memory: 67 GB total, with 61 GB free (so I don’t think it’s a memory issue). System load: 1.15, 0.42, 0.16 . Using Node.js version 22.14.0. I asked Grok what might be the problem: From what I’ve read, it could be something about too many processes trying to write to the console at once, causing a jam. Updating Discourser from SSH ./launcher works normally. I haven’t tried much to fix it yet because I’m not sure where to start. Has anyone seen this before? Thanks for any help!

[image] Brian: Error: assets/chunk.cbb4d6362a2090db10ec.d41d8cd9.js from Terser plugin failed to handle: failed printing to stdout: Resource temporarily unavailable (os error 11) Could be a shortage of virtual memory: try adding RAM or adding swap. (Fork failing with EAGAIN can be memory shortage) Have a look at free -h vmstat 5 5 There are two kernel tunables which can improve memory efficiency cat /proc/sys/vm/overcommit_memory cat /sys/kernel/mm/transparent_hugepage/enabled (See MKJ’s Opinionated Discourse Deployment Configuration)

@Ed_S thank you. I have 61 GB of RAM available out of 67. Could it still be virtual memory?

That’s a lot, but vmstat and free can tell us how it’s used. Have you checked dmesg output for messages about memory and OOM? How big is your database?

Sorry for the delayed response. The issue seemed to go away without understanding why. I think it was/is a plugin because I disabled them all and the site updated normally for admin panel. I expected the issue to return when re-enabled the plugins, but it did not. I will need to check again if it returns. Thanks for the assistance.

Discourse update error with Terser

Product Support

pfaffman (Jay Pfaffman) March 1, 2025, 1:30am 5

Have you run a command line rebuild lately? Have you seen PostgreSQL 15 update

Topic		Replies	Views
Can't update Discourse + Error 500 Product Support	1	370	January 30, 2024
Crash after attempting to update Bug	14	577	May 19, 2026
I keep getting errors when updating Product Support	26	743	July 16, 2025
Discourse Fails to update in the Admin UI - No matter what Self-hosting	31	1119	August 5, 2025
Sorry, there was an error upgrading Discourse Product Support	2	624	November 26, 2022

Discourse update error with Terser

Related topics