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 #<Process::Status: pid 505 exit 1> Location of failure: /usr/local/lib/ruby/gems…

[이미지] 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 g…

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/disc…

Chris with all respect, can we not complicate one support request with logs from another installation? :sweat_smile: [이미지] 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, regardles…

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 may be related, but we won’t know until the OP has provided more detail.

[이미지] 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.

[이미지] 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 Fail…

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.

[이미지] 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. [이미지] 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 …

Bootstrap failed error after upgrading my server

지원 자체 호스팅

merefield (Robert) 9월 27, 2023, 6:02오전 2

we would need more information.

Failed to Bootstrap after upgrade

글		댓글	조회수
Failed to Bootstrap after upgrade Self-hosting	11	1080	9월 27, 2023
Bootstrap failure during most recent upgrade Self-hosting	6	653	2월 3, 2023
Failed to bootstrap - pups Self-hosting	5	464	10월 21, 2023
Error upgrading, failed to bootstrap Self-hosting	20	1975	3월 26, 2022
Discourse upgrade error "FAILED TO BOOTSTRAP" Support	14	2156	9월 3, 2021

Bootstrap failed error after upgrading my server

Related topics