Prompted by the Dashboard saying that 3.2.0.beta4 was an urgent upgrade, but this has failed to build. Prompted by the error message, I was directed to look at bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/rbtrace-0.5.1/mkmf.log This was building msgpack, with the following error: LD_LIBRARY_PATH=.:/usr/local/lib "./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" ls: cannot access '.': Operation not permitted configure: error: working directory cannot be determined Help please! I’d prefer not to rebuild from the backup. Edit: I have run git pull and ./launcher rebuild app.

OK so I think rbtrace may be relying on the modernity of the background OS for some reason, see this advice: [image] Discourse Build Error: “An error occurred while installing rbtrace (0.5.1), and Bundler cannot continue Self-hosting 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. So it looks like advice is to migrate to new server to expedite OS upgrade.

Are you able/willing to rebuild on tests-passed? I suspect latest beta tag is impacted by this “transient” dependency error that has since cleared on latest. Either that or wait for next beta and just restart your container and sit there? [image] Discourse Build Error: “An error occurred while installing rbtrace (0.5.1), and Bundler cannot continue Self-hosting 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 pa…

[image] Robert: Are you able/willing to rebuild on tests-passed? I suspect latest beta tag is impacted by this “transient” dependency error that has since cleared on latest. Either that or wait for next beta and just restart your container and sit there? How do I switch to tests-passed?

Edit app.yml for version: tests-passed then rebuild

Alas, no joy: I, [2024-01-11T11:06:29.588530 #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 ***

It was worth a try, this will require more research. This gem having been involved in lots of failed builds recently is suspicious.

Yeah, this is the current version: ~/discourse$ gem info rbtrace *** LOCAL GEMS *** rbtrace (0.5.1, 0.5.0, 0.4.14)

So is this the image, or the basse ubuntu that needs updating?

I read that as base Ubuntu. For the record, what version are you on? (might help others)

Funnily enough I’ve not had problems on Jammy (@JammyDodger aha) :/var/discourse/containers# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.3 LTS Release: 22.04 Codename: jammy

3.2.0.beta4 failed to build -- Site down

Product Support Self-hosting

Alexander_Wright (Alexander Wright) January 11, 2024, 11:21am 11

Welcome to Ubuntu 20.04.6 LTS (GNU/Linux 5.4.0-169-generic x86_64)

I’ll do a release upgrade to see if that helps.

Topic		Replies	Views
Discourse Build Error: “An error occurred while installing rbtrace (0.5.1), and Bundler cannot continue Self-hosting	20	3056	January 25, 2024
Upgrade from 3.1.1 to 3.2.0 failing Self-hosting	3	500	February 1, 2024
Rebuild failure: "extconf failed, exit code 1" -- due to old Docker? Self-hosting	10	1912	February 21, 2024
Update Fails with Unexpected Error During Rebuild Self-hosting	9	1465	December 16, 2023
Rebuild failed - FAILED TO BOOTSTRAP Self-hosting	20	2351	December 28, 2023

3.2.0.beta4 failed to build -- Site down

Related topics