3.2.0.beta4 failed to build -- Site down

installation
1

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.

2

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?

3

How do I switch to tests-passed?

4

Edit app.yml for

version: tests-passed

then rebuild

1 Like
5

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 ***

1 Like
6

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

7

Yeah, this is the current version:

~/discourse$ gem info rbtrace

*** LOCAL GEMS ***

rbtrace (0.5.1, 0.5.0, 0.4.14)
8

OK so I think rbtrace may be relying on the modernity of the background OS for some reason, see this advice:

So it looks like advice is to migrate to new server to expedite OS upgrade.

3 Likes
9

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

10

I read that as base Ubuntu.

For the record, what version are you on? (might help others)

2 Likes
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.

1 Like
12

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
13

Arrgh!

Sorry, this storage driver is not supported in kernels for newer
releases

There will not be any further Ubuntu releases that provide kernel
support for the aufs storage driver.

Please ensure that none of your containers are using the aufs storage
driver, remove the directory /var/lib/docker/aufs and try again.

How do I change the storage driver?

1 Like
14

Someone helpfully wrote a guide:

2 Likes
15

I took this advice, and am now back up and running. Thank you @merefield for your assistance.

1 Like
16

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.