Today after several months of not upgrading, I upgraded docker manager successfully and then tried to upgrade docker, which failed during bundling. I tried to rebuild the container using ./launcher rebuild app but it failed on exactly the same place. Now when I start the app, I get this error on the web console and a blank page: Uncaught Error: There is no route named user

First thing to check is your plugins – do they need updating too? Perhaps you are using an old plugin that is no longer compatible with Discourse.

I just tried the upgrade again, here’s where it blows up: I, [2015-09-23T15:49:08.096530 #285] INFO -- : Writing /var/www/discourse/public/assets/spinner_96-8091be87c9cf1abef73e3899ec7645c1.gif I, [2015-09-23T15:49:48.583254 #285] INFO -- : Writing /var/www/discourse/public/assets/admin-65c6808be982448a35912489faa998d1.js [169] 23 Sep 15:52:41.064 * 10 changes in 300 seconds. Saving... [169] 23 Sep 15:52:41.065 * Background saving started by pid 959 [959] 23 Sep 15:52:41.350 * DB saved on disk [959] 23 Sep 15:52:41.351 * RDB: 38 MB of memory used by copy-on-write [169] 23 Sep 15:52:41.367 * Background saving terminated with success I, [2015-09-23T15:54:29.630194 #285] INFO -- : Writing /var/www/discourse/public/assets/application-985117f83083528097778adfdbb2ee68.js rake aborted! SignalException: SIGTERM /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/sprockets/asset.rb:151:in `write' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/sprockets/asset.rb:151:in `block in write_to' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/sprockets/asset.rb:146:in `open' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/sprockets/asset.rb:146:in `write_to' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/sprockets/manifest.rb:135:in `block in compile' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/sprockets/manifest.rb:118:in `each' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/sprockets/manifest.rb:118:in `compile' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-rails-2.0.1/lib/sprockets/rails/task.rb:60:in `block (3 levels) in define' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/rake/sprocketstask.rb:146:in `with_logger' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-rails-2.0.1/lib/sprockets/rails/task.rb:59:in `block (2 levels) in define' Tasks: TOP => assets:precompile (See full trace by running task with --trace) zlib(finalizer): Zlib::GzipWriter object must be closed explicitly. zlib(finalizer): the stream was freed prematurely. /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus.rb:437:in `kill': No such process (Errno::ESRCH) from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus.rb:437:in `block (2 levels) in new_subscriber_thread' from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus.rb:434:in `fork' from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus.rb:434:in `block in new_subscriber_thread' from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus/timer_thread.rb:98:in `call' from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus/timer_thread.rb:98:in `do_work' from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus/timer_thread.rb:29:in `block in initialize' I, [2015-09-23T15:54:39.790839 #38] INFO -- : Purging temp files Bundling assets I, [2015-09-23T15:54:39.791353 #38] INFO -- : Terminating async processes

[imagem] shadowhand: SignalException: SIGTERM Weird, that implies that something terminated the upgrade like a Ctrl+c? I also haven’t seen the Zlib::GzipWriter error before. Looks like something is preventing the upgrade from finishing.

I didn’t abort the upgrade. Have seen this same error 3 times now.

Same thing again just now, with slightly more info: [176] 23 Sep 16:33:25.034 * Background saving started by pid 967 [967] 23 Sep 16:33:25.326 * DB saved on disk [967] 23 Sep 16:33:25.327 * RDB: 4 MB of memory used by copy-on-write [176] 23 Sep 16:33:25.335 * Background saving terminated with success rake aborted! SignalException: SIGTERM /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/sprockets/index.rb:70:in `block in find_asset' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/sprockets/index.rb:69:in `instance_eval' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/sprockets/index.rb:69:in `find_asset' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/sprockets/manifest.rb:211:in `block in find_asset' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/sprockets/manifest.rb:257:in `benchmark' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/sprockets/manifest.rb:210:in `find_asset' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/sprockets/manifest.rb:119:in `block in compile' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/sprockets/manifest.rb:118:in `each' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/sprockets/manifest.rb:118:in `compile' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-rails-2.0.1/lib/sprockets/rails/task.rb:60:in `block (3 levels) in define' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-2.11.0/lib/rake/sprocketstask.rb:146:in `with_logger' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sprockets-rails-2.0.1/lib/sprockets/rails/task.rb:59:in `block (2 levels) in define' Tasks: TOP => assets:precompile (See full trace by running task with --trace) /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus.rb:437:in `kill': No such process (Errno::ESRCH) from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus.rb:437:in `block (2 levels) in new_subscriber_thread' from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus.rb:434:in `fork' from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus.rb:434:in `block in new_subscriber_thread' from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus/timer_thread.rb:98:in `call' from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus/timer_thread.rb:98:in `do_work' from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.16/lib/message_bus/timer_thread.rb:29:in `block in initialize' I, [2015-09-23T16:34:56.867208 #45] INFO -- : Purging temp files Bundling assets I, [2015-09-23T16:34:56.867787 #45] INFO -- : Terminating async processes I, [2015-09-23T16:34:56.867971 #45] INFO -- : Sending TERM to sudo -u postgres /usr/lib/postgresql/9.3/bin/postmaster -D /etc/postgresql/9.3/main pid: 85 I, [2015-09-23T16:34:56.868152 #45] INFO -- : Sending TERM to sudo -u redis /usr/bin/redis-server /etc/redis/redis.conf pid: 174 2015-09-23 16:34:56 UTC LOG: received smart shutdown request [176 | signal handler] (1443026096) Received SIGTERM, scheduling shutdown...2015-09-23 16:34:56 UTC LOG: autovacuum launcher shutting down 2015-09-23 16:34:56 UTC LOG: shutting down 2015-09-23 16:34:56 UTC LOG: database system is shut down [176] 23 Sep 16:34:56.960 # User requested shutdown... [176] 23 Sep 16:34:56.960 * Saving the final RDB snapshot before exiting. [176] 23 Sep 16:34:57.240 * DB saved on disk [176] 23 Sep 16:34:57.240 # Redis is now ready to exit, bye bye... FAILED -------------------- RuntimeError: cd /var/www/discourse && sudo -E -u discourse bundle exec rake assets:precompile failed with return # Location of failure: /pups/lib/pups/exec_command.rb:105:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"web", "cmd"=>["gem update bundler", "mkdir -p /shared/vendor_bundle", "cp -fr /shared/vendor_bundle/* vendor/bundle || echo \"can not copy\"", "chown -R discourse $home", "sudo -E -u discourse bundle install --deployment --verbose --without test --without development", "cp -fr vendor/bundle/* /shared/vendor_bundle", "sudo -E -u discourse bundle exec rake db:migrate", "sudo -E -u discourse bundle exec rake assets:precompile"]} 95c4e6c3dc8d1b6cb5efca65dfa15847f71cfc61701cf05c47adc0fc91cb8039 FAILED TO BOOTSTRAP

The error seems to be related to message bus killing another process. I’m not so familiar with that gem but maybe @sam can jump in and give some advice?

What’s your server environment? This looks like somehow some strange supervisor tool kills processes that run too long or cause too high CPU loads…

$ cat /etc/issue Ubuntu 14.04.1 LTS Running on Rackspace Cloud.

They don’t seem to enforce something like that by default - can you send me a ps auxf output (if you like, via PM)?

Upgrade failed due to process terminating

Product Support Self-hosting

shadowhand (Woody Gilk) 23 Setembro , 2015 15:59 4

I don’t believe I am using any 3rd party plugins.

Tópico		Respostas	Vistas
Down after Docker Update Self-hosting server-resources	6	756	6 Novembro , 2020
Docker Manager: FAILED TO UPGRADE Self-hosting docker-manager , server-resources	6	1431	4 Novembro , 2020
"Waiting for unicorn to reload", then update stops Product Support	30	5134	20 Junho , 2021
Automatic upgrade from 2.6.0.beta5 to 2.7.0.beta3 failed Self-hosting	8	1583	26 Abril , 2021
Error while updating through launcher rebuild Self-hosting	2	675	16 Abril , 2024

Upgrade failed due to process terminating

Related topics