After applying the latest set of patches I’m getting a bootstrap failure… FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' 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"=>"db_migrate", "cmd"=>["su discourse -c 'bundle exec rake db:migrate'"]} 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. The logs show… I, [2023-09-27T09:27:53.120283 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db: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 ` ' /usr/local/bin/bundle:25:in `load' /usr/local/bin/bundle:25:in ` ' (See full trace by running task with --trace) I’m currently trying various things to bring my forum back to life.

No reason to ask things twice, especially when I already said there would be a fix available soon. The new version of discourse-migratepassword is available now. Just rebuild.

This appears to be related to the migratepassword plugin. I can rebuild the forum with all plugins disabled but I get the bootstrap failure if I try to rebuild with only the migratepassword plugin enabled.

[image] Chris McMahon: This appears to be related to the migratepassword plugin. I’ll add a little ping for @RGJ as he may know more. :crossed_fingers:

Yes, this broke yesterday due to an updated dependency in core, the PR is already on my to-do-list and will be available later today or tomorrow. quick fixes: Option 1 check out Discourse 91c94f which is the commit before the breaking change Option 2 change gem 'ffi', '1.15.5', require: false in the plugin to gem 'ffi', '1.16.2', require: false

[image] Richard - Communiteq: Option 1 check out Discourse 91c94f which is the commit before the breaking change Option 2 change gem 'ffi', '1.15.5', require: false in the plugin to gem 'ffi', '1.16.2', require: false Not sure how to do either of those. I did try putting “version: 91c94f” into app.yml but that didn’t help so I probably did the wrong thing. I’ll just run without the plugin until the PR is ready. The vast majority of my users have already migrated from their old passwords, but there are one or two ‘legacy users’ each week who surface again from a few years ago.

What are the cmd for this or where is the file located for me to change this?

[image] Richard - Communiteq: 91c94f in this case how would I do that in the console I mean, the cmd to execute

[image] Richard - Communiteq: The new version of discourse-migratepassword is available now. Thanks for the fix Richard. Now rebuilt without errors :grinning:

[image] Richard - Communiteq: discourse-migratepassword do you have discourse-migratepassword in your plugins? because I have tried rebuilding it and I’m still having the same issue. es:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 42 2023-09-27 16:50:33.227 UTC [42] LOG: received fast shutdown request I, [2023-09-27T16:50:33.227763 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 111 111:signal-handler (1695833433) Received SIGTERM scheduling shutdown... 2023-09-27 16:50:33.252 UTC [42] LOG: aborting any active transactions 2023-09-27 16:50:33.262 UTC [42] LOG: background worker "logical replication launcher" (PID 51) exited with exit code 1 2023-09-27 16:50:33.265 UTC [46] LOG: shutting down 2023-09-27 16:50:33.282 UTC [42] LOG: database system is shut down 111:M 27 Sep 2023 16:50:33.282 # User requested shutdown... 111:M 27 Sep 2023 16:50:33.283 * Saving the final RDB snapshot before exiting. 111:M 27 Sep 2023 16:50:33.295 * DB saved on disk 111:M 27 Sep 2023 16:50:33.296 # Redis is now ready to exit, bye bye... 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. 92863be4bda311c642a83b1afd97e58a64e9044ea2dc0e23f245fafb086851f7

[image] john shim: do you have discourse-migratepassword in your plugins? [image] Chris McMahon: This appears to be related to the migratepassword plugin. I can rebuild the forum with all plugins disabled but I get the bootstrap failure if I try to rebuild with only the migratepassword plugin enabled. As he wrote he has. If you don’t, maybe you continue in the topic you started and share the full error message [image]Bootstrap failed error after upgrading my server [image]Bootstrap failed error after upgrading my server please scroll up and look for earlier error messages :arrow_double_up: :eyes: we would need more information.

Failed to Bootstrap after upgrade

Product Support Self-hosting

shim (john shim) September 27, 2023, 4:43pm 10

im still having the same issue, and I don’t have discourse-migratepassword in my plugin

Topic		Replies	Views
Bootstrap failed error after upgrading my server Self-hosting	13	1521	September 27, 2023
Failed to bootstrap - pups Self-hosting	5	497	October 21, 2023
Failed to Bootstrap after running launcher rebuild app Self-hosting	3	624	October 7, 2022
Troubleshooting bootstrap failures in Discourse Self-hosting	13	485	July 28, 2025
Bootstrap failure during most recent upgrade Self-hosting	6	700	February 3, 2023

Failed to Bootstrap after upgrade

Related topics