I saw that a few official plugins needed updating, as well as my Discourse version. Just a new commit hash, nothing major. However, after letting it do its thing, I get the dreaded ‘Oops The software powering this discussion forum encountered an unexpected problem. We apologize for the inconvenience.’ Here are the errors in /logs: [List of errors and messages on a monitoring screen for web servers or applications. (Captioned by AI)] Here is the one with the 89 messages reported: Message (89 copies reported) Failed to warm up pretty text: JavaScript was terminated (either by timeout or explicitly) /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_racer-0.14.1/lib/mini_racer.rb:237:in `eval_unsafe' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_racer-0.14.1/lib/mini_racer.rb:237:in `block (2 levels) in eval' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_racer-0.14.1/lib/mini_racer.rb:378:in `timeout' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_racer-0.14.1/lib/mini_racer.rb:236:in `block in eval' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_racer-0.14.1/lib/mini_racer.rb:234:in `synchronize' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_racer-0.14.1/lib/mini_racer.rb:234:in `eval' /var/www/discourse/lib/discourse_js_processor.rb:98:in `create_new_context' /var/www/discourse/lib/discourse_js_processor.rb:114:in `block in v8' /var/www/discourse/lib/discourse_js_processor.rb:112:in `synchronize' /var/www/discourse/lib/discourse_js_processor.rb:112:in `v8' /var/www/discourse/lib/discourse_js_processor.rb:127:in `block in v8_call' /var/www/discourse/lib/discourse_js_processor.rb:126:in `synchronize' /var/www/discourse/lib/discourse_js_processor.rb:126:in `v8_call' /var/www/discourse/lib/discourse_js_processor.rb:151:in `perform' /var/www/discourse/lib/pretty_text.rb:34:in `apply_es6_file' /var/www/discourse/lib/pretty_text.rb:41:in `block in ctx_load_directory' /var/www/discourse/lib/pretty_text.rb:39:in `each' /var/www/discourse/lib/pretty_text.rb:39:in `ctx_load_directory' /var/www/discourse/lib/pretty_text.rb:77:in `create_es6_context' /var/www/discourse/lib/pretty_text.rb:136:in `block in v8' /var/www/discourse/lib/pretty_text.rb:134:in `synchronize' /var/www/discourse/lib/pretty_text.rb:134:in `v8' /var/www/discourse/lib/pretty_text.rb:177:in `block in markdown' /var/www/discourse/lib/pretty_text.rb:686:in `block in protect' /var/www/discourse/lib/pretty_text.rb:686:in `synchronize' /var/www/discourse/lib/pretty_text.rb:686:i... Backtrace /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/broadcast_logger.rb:134:in `block in error' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/broadcast_logger.rb:231:in `block in dispatch' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/broadcast_logger.rb:231:in `each' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/broadcast_logger.rb:231:in `dispatch' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/broadcast_logger.rb:134:in `error' /var/www/discourse/lib/discourse.rb:947:in `rescue in after_fork' /var/www/discourse/lib/discourse.rb:943:in `after_fork' /var/www/discourse/lib/demon/base.rb:248:in `establish_app' /var/www/discourse/lib/demon/base.rb:183:in `block in run' /var/www/discourse/lib/demon/base.rb:180:in `fork' /var/www/discourse/lib/demon/base.rb:180:in `run' /var/www/discourse/lib/demon/base.rb:173:in `start' /var/www/discourse/lib/demon/base.rb:93:in `restart' /var/www/discourse/lib/demon/sidekiq.rb:36:in `block in heartbeat_check' /var/www/discourse/lib/demon/sidekiq.rb:27:in `each' /var/www/discourse/lib/demon/sidekiq.rb:27:in `heartbeat_check' config/unicorn.conf.rb:131:in `block (2 levels) in reload' Do let me know if you would like the errors of any of the other ones.

Have you tried a ./launcher rebuild app

@pfaffman I can close the terminal and it will still run in the background, correct?

If you want this, you need to use a session manager like screen or tmux.

If you’re asking that question, the answer is “No,” and you should keep the terminal open and at least check that it finished without errors. What you should probably do is keep it open in one window that you can see while you do something less boring tha watching text scroll by in another window. If your question is “how can I keep a ssh session running so that it won’t close when I disconnect and I can reconnect to it later” then you should find out about screen or tmux. It seems to me like your understanding of how terminal sessions work is such that just keeping the terminal open is the best course of action for you.

Rebuilt the forum and it’s working now.

Forum not up after 'Update all'

Product Support

NateDhaliwal (Nate Dhaliwal) January 6, 2025, 11:04am 3

Never thought of that, lol. Will run it, thanks!

Topic		Replies	Views
Failed to warm up pretty text Product Support	4	715	February 22, 2022
One admin restarted the forum while another was updating. How to fix Product Support	2	591	October 19, 2022
Failed to warm up pretty text: JavaScript was terminated Product Support	4	586	February 14, 2022
Oops The software powering this discussion forum encountered an unexpected problem Product Support	9	638	December 31, 2024
Discourse update error with Terser Product Support	5	281	March 11, 2025

Forum not up after 'Update all'

Related topics