im having issues rebuilding my forum after upgrading the server on linode FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle config --local deployment true' failed with return # Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle config --local deployment true'", "su discourse -c 'bundle config --local without \"development test\"'", "su discourse -c 'bundle install --retry 3 --jobs 4'"]} bootstrap failed with exit code 1 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one. ./discourse-doctor may help diagnose the problem.

[image] john shim: please scroll up and look for earlier error messages :arrow_double_up: :eyes: we would need more information.

I’m seeing a similar error. I’ve tried a rebuild with all but two plugins disabled (docker-manager and migrate passwords) so I don’t think it’s plugin related. I ran discourse-doctor but the only occurrence of ‘error’ is the description of how to search for the word error. Unfortunately I have to go out to an appointment now but I’ll look for other issues when I get back.

Does this give any clues… SKIP_POST_DEPLOYMENT_MIGRATIONS=1 bundle exec rake multisite:migrate rake aborted! Gem::LoadError: can't activate ffi-1.15.5, already activated ffi-1.16.2 /var/www/discourse/lib/plugin_gem.rb:25:in `load' /var/www/discourse/lib/plugin/instance.rb:825:in `gem' /var/www/discourse/plugins/discourse-migratepassword/plugin.rb:28:in `activate!' /var/www/discourse/lib/plugin/instance.rb:722:in `instance_eval' /var/www/discourse/lib/plugin/instance.rb:722:in `activate!' /var/www/discourse/lib/discourse.rb:347:in `block in activate_plugins!' /var/www/discourse/lib/discourse.rb:344:in `each' /var/www/discourse/lib/discourse.rb:344:in `activate_plugins!' /var/www/discourse/config/application.rb:227:in `block in ' /var/www/discourse/lib/plugin.rb:6:in `initialization_guard' /var/www/discourse/config/application.rb:227:in ` ' /var/www/discourse/config/application.rb:75:in ` ' /var/www/discourse/config/application.rb:74:in ` ' :38:in `require' :38:in `require' /var/www/discourse/Rakefile:7:in ` ' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/rake-13.0.6/exe/rake:27:in ` ' /var/www/discourse/vendor/bundle/ruby/3.2.0/bin/bundle:25:in `load' /var/www/discourse/vendor/bundle/ruby/3.2.0/bin/bundle:25:in ` ' (See full trace by running task with --trace) Docker Manager: FAILED TO UPGRADE # /var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:209:in `run' /var/www/discourse/plugins/docker_manager/lib/docker_manager/upgrader.rb:108: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.2.2/lib/thor/command.rb:27:in `run' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/thor-1.2.2/lib/thor/invocation.rb:127:in `invoke_command' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/thor-1.2.2/lib/thor.rb:392: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 ` ' :38:in `require' :38:in `require' /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/bootsnap-1.16.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require' bin/rails:18:in ` ' Spinning up 7 Unicorn worker(s) that were stopped initially

Chris with all respect, can we not complicate one support request with logs from another installation? :sweat_smile: [image] Chris McMahon: I’m seeing a similar error. Because that text appears pretty much under every single rebuild that has failed due to an error during the process, regardless of the root cause.

OK, I wasn’t aware that the same error appeared for multiple causes. I just knew the errors looked very similar, if not identical when viewed on my phone and as they occurred from what appeared to be the same set of patches I assumed they might be related. I’ll start a new thread with my problems in it.

It may be related, but we won’t know until the OP has provided more detail.

[image] Robert: It may be related Actually the helpful nature of Discourse isn’t helpful here. When I started to report the problem I got the “Your post looks similat to this one” which encourages you not to create a new post.

[image] Chris McMahon: rebuild with all but two plugins disabled (docker-manager and migrate passwords) Migrate password is broken. It’ll be fixed soon. Rebuild without it or restart your old container. There is another topic about it but I can’t find it. Oh, I see now, it was your topic Failed to Bootstrap after upgrade - #4 by RGJ Here’s what to do @shim

Thank you I have the same issue on 2 forums and that happened after the patch update however the fix was suggested … I have no idea how to go about it. it would be helpful if they pushed the new PR so that we can update it via the console.

[image] john shim: it would be helpful if they pushed the new PR so that we can update it via the console. Here’s what he said in the other topic. [image]Failed to Bootstrap after upgrade the PR is already on my to-do-list and will be available later today or tomorrow. That’s pretty good service if you ask me.

Bootstrap failed error after upgrading my server

Product Support Self-hosting

pfaffman (Jay Pfaffman) September 27, 2023, 4:00pm 11

Here’s what he said in the other topic.

That’s pretty good service if you ask me.

Topic		Replies	Views
Failed to Bootstrap after upgrade Self-hosting	11	1174	September 27, 2023
Bootstrap failure during most recent upgrade Self-hosting	6	700	February 3, 2023
Failed to bootstrap - pups Self-hosting	5	497	October 21, 2023
Error upgrading, failed to bootstrap Self-hosting	20	2172	March 26, 2022
Discourse upgrade error "FAILED TO BOOTSTRAP" Product Support	14	2219	September 3, 2021

Bootstrap failed error after upgrading my server

Related topics