For the past few weeks or so, we cannot rebuild our Discourse forum software. Each time, we get this Bundler error: occurred while installing rbtrace (0.5.1), and Bundler cannot continue. FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle install --retry 3 --jobs 4' failed with return # Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132: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 5 ** 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. dfd1d73cc65b60ab8b8963ad9bdb005500322808bf8766cf90c07c91d3dea615ype or paste code here With success using this reference: https://github.com/rubinius/rubinius/issues/3327 Building native extensions with: '--with-cflags=-Wno-implicit-function-declaration' This could take a while... Successfully installed rbtrace-0.5.1 Parsing documentation for rbtrace-0.5.1 Done installing documentation for rbtrace after 0 seconds 1 gem installed But it keeps failing An error occurred while installing rbtrace (0.5.1), and Bundler cannot continue. Any suggestion? Or are we doomed, and need to rebuild Discourse from scratch in an entire new directory structure and change all our admin scripts, etc.

I think there’s also been another report of that today (with a reference to another as well), though I’m not sure a solution has been found yet other than a new droplet - Rebuild failed - FAILED TO BOOTSTRAP - #4 by Firepup650

I am having this same error and it seems to have zonked my install. Any idea what to do to fix?

@dylanb @Victor_Berridge what is your OS, kernel and OS version?

I’m seeing quite a few of these failing in the last few weeks, here’s another two for reference: [image] Another discourse offline "bootstrap failed with exit code 5" Self-hosting Hello Community! I’m sorry we have to meet under these circumstances. Discourse is offline after a failed upgrade. Same story as. Discourse offline after failed upgrade "bootstrap failed with exit code 5" Attempted to upgrade to v3.2.0.beta3 I’m still on Ubuntu 16.04. I DO have the previous docker images fortunately (I hope), but I’m not sure what to do to restore services. Also using DigitalOcean. Error FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse … [image] Discourse offline after failed upgrade "bootstrap failed with exit code 5" Self-hosting Hi everyone, My Discourse is currently offline cry pensive It failed after trying to upgrade this morning from/to v3.2.0.beta3 +468: On the command line, the error message is: And the full console log: root@greyarro:~# cd /var/discourse/ root@greyarro:/var/discourse# git pull Already up to date. root@greyarro:/var/discourse# ./launcher rebuild app x86_64 arch detected. WARNING: containers/app.yml file is world-readable. You can secure this file by running: chmod o-rwx containers/app.… And three others: [image] Rebuild failed - FAILED TO BOOTSTRAP Self-hosting Been a while since this forum was updated, getting this message after a git pull and rebuild: FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle install --retry 3 --jobs 4' failed with return # Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle config --local deploy… [image] Update Fails with Unexpected Error During Rebuild Self-hosting Hi Everyone, I’m stuck with a Discourse update issue. The rebuild command fails, and I can’t complete the update. It’s related to the bundle install step… FAILED Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle install --retry 3 --jobs 4' failed with return # Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle config --local deplo… [image] Rebuild failure: "extconf failed, exit code 1" -- due to old Docker? Self-hosting I’ve got a rebuild that’s failing, I think due to this. It’s running Ubuntu 16.04 with Docker version 17.05.0-ce, build 89658be, which I know is suspect, but I wanted to give this person one more rebuild if at all possible. I, [2023-12-06T16:10:12.656984 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle install --retry 3 --jobs 4' Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/rbtrace-0.5.0/… Plus this actual topic, makes six that I found with just a quick search. Can anyone spot a commonality with all of these recently-failing instances? :thinking:

I also seem to have run into this issue, unfortunately. I, [2024-01-06T19:38:58.925098 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle install --retry 3 --jobs 4' Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/rbtrace-0.5.1/ext /usr/local/bin/ruby extconf.rb -- tar zxvfo msgpack-1.1.0.tar.gz -- env CFLAGS=nil LDFLAGS=nil CC=nil -- ./configure --disable-dependency-tracking --disable-shared --with-pic --prefix=/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/rbtrace-0.5.1/ext/dst/ --libdir=/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/rbtrace-0.5.1/ext/dst/lib *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/usr/local/bin/$(RUBY_BASE_NAME) extconf.rb:6:in `sys': ./configure --disable-dependency-tracking --disable-shared --with-pic --prefix=/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/rbtrace-0.5.1/ext/dst/ --libdir=/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/rbtrace-0.5.1/ext/dst/lib failed, please report to https://github.com/tmm1/rbtrace/issues (RuntimeError) from extconf.rb:42:in `block (2 levels) in ' from extconf.rb:34:in `chdir' from extconf.rb:34:in `block in ' from extconf.rb:30:in `chdir' from extconf.rb:30:in ` ' To see why this extension failed to compile, please check the mkmf.log which can be found here: /var/www/discourse/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/rbtrace-0.5.1/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /var/www/discourse/vendor/bundle/ruby/3.2.0/gems/rbtrace-0.5.1 for inspection. Results logged to /var/www/discourse/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/rbtrace-0.5.1/gem_make.out /usr/local/lib/ruby/site_ruby/3.2.0/rubygems/ext/builder.rb:125:in `run' /usr/local/lib/ruby/site_ruby/3.2.0/rubygems/ext/ext_conf_builder.rb:28:in `build' /usr/local/lib/ruby/site_ruby/3.2.0/rubygems/ext/builder.rb:193:in `build_extension' /usr/local/lib/ruby/site_ruby/3.2.0/rubygems/ext/builder.rb:227:in `block in build_extensions' /usr/local/lib/ruby/site_ruby/3.2.0/rubygems/ext/builder.rb:224:in `each' /usr/local/lib/ruby/site_ruby/3.2.0/rubygems/ext/builder.rb:224:in `build_extensions' /usr/local/lib/ruby/site_ruby/3.2.0/rubygems/installer.rb:852:in `build_extensions' /usr/local/lib/ruby/gems/3.2.0/gems/bundler-2.4.13/lib/bundler/rubygems_gem_installer.rb:72:in `build_extensions' /usr/local/lib/ruby/gems/3.2.0/gems/bundler-2.4.13/lib/bundler/rubygems_gem_installer.rb:28:in `install' /usr/local/lib/ruby/gems/3.2.0/gems/bundler-2.4.13/lib/bundler/source/rubygems.rb:198:in `install' /usr/local/lib/ruby/gems/3.2.0/gems/bundler-2.4.13/lib/bundler/installer/gem_installer.rb:54:in `install' /usr/local/lib/ruby/gems/3.2.0/gems/bundler-2.4.13/lib/bundler/installer/gem_installer.rb:16:in `install_from_spec' /usr/local/lib/ruby/gems/3.2.0/gems/bundler-2.4.13/lib/bundler/installer/parallel_installer.rb:156:in `do_install' /usr/local/lib/ruby/gems/3.2.0/gems/bundler-2.4.13/lib/bundler/installer/parallel_installer.rb:147:in `block in worker_pool' /usr/local/lib/ruby/gems/3.2.0/gems/bundler-2.4.13/lib/bundler/worker.rb:62:in `apply_func' /usr/local/lib/ruby/gems/3.2.0/gems/bundler-2.4.13/lib/bundler/worker.rb:57:in `block in process_queue' /usr/local/lib/ruby/gems/3.2.0/gems/bundler-2.4.13/lib/bundler/worker.rb:54:in `loop' /usr/local/lib/ruby/gems/3.2.0/gems/bundler-2.4.13/lib/bundler/worker.rb:54:in `process_queue' /usr/local/lib/ruby/gems/3.2.0/gems/bundler-2.4.13/lib/bundler/worker.rb:90:in `block (2 levels) in create_threads' An error occurred while installing rbtrace (0.5.1), and Bundler cannot continue. In Gemfile: rbtrace I, [2024-01-06T19:39:23.286237 #1] INFO -- : Fetching gem metadata from https://rubygems.org/......... sudo lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.4 (stretch) Release: 9.4 Codename: stretch docker -v Docker version 19.03.14, build 5eb3275d40 Tried cloning docker_discourse anew (commit fcce1376043adeb09e21ec1ec079a41e4d29fe6e), copying over app.yaml and shared/ and running rebuild. Same issue.

[image] Daniel Correia: Debian GNU/Linux 9.4 (stretch) Debian 9 has been superseded by Debian 10 (“buster”). Security updates have been discontinued as of July 6th, 2020. You may want to take your backup and migrate to a new server running a current OS version.

Thanks for the advice - that’s a good idea.

[image] Richie Rich: Can anyone spot a commonality with all of these recently-failing instances? :thinking: Anyone…? :thinking: :person_shrugging: Something important must have changed recently to cause all of these Discourse instances to suddenly start failing at the same time?

So far the only link is very old OS/Kernel.

That seems to be the common denominator, but why? Did something change in Ruby recently? :thinking: :person_shrugging:

Discourse Build Error: “An error occurred while installing rbtrace (0.5.1), and Bundler cannot continue

Product Support Self-hosting

merefield (Robert) January 11, 2024, 7:24pm 17

You need to be on at least Ubuntu Jammy (22 LTS) for the latest beta or tests-passed build to now work I believe.

16.x is ancient

Topic		Replies	Views
Upgrade from 3.1.1 to 3.2.0 failing Self-hosting	3	494	February 1, 2024
Rebuild failure: "extconf failed, exit code 1" -- due to old Docker? Self-hosting	10	1902	February 21, 2024
3.2.0.beta4 failed to build -- Site down Self-hosting	14	829	January 11, 2024
Rebuild failed - FAILED TO BOOTSTRAP Self-hosting	20	2343	December 28, 2023
Discourse offline after failed upgrade "bootstrap failed with exit code 5" Self-hosting	24	1739	February 22, 2024

Discourse Build Error: “An error occurred while installing rbtrace (0.5.1), and Bundler cannot continue

Related topics