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

[Richie (Richie Rich)]

I’m seeing quite a few of these failing in the last few weeks, here’s another two for reference:

Another discourse offline "bootstrap failed with exit code 5"

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 …

Discourse offline after failed upgrade "bootstrap failed with exit code 5"

Hi everyone, My Discourse is currently offline 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:

Rebuild failed - FAILED TO BOOTSTRAP

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 #<Process::Status: pid 502 exit 5> 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…

Update Fails with Unexpected Error During Rebuild

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 #<Process::Status: pid 6677 exit 5> 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…

Rebuild failure: "extconf failed, exit code 1" -- due to old Docker?

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?