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
.
merefield
(Robert)
January 11, 2024, 10:53am
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?
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 #<Process::Status: pid 541 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 pa…
How do I switch to tests-passed?
merefield
(Robert)
January 11, 2024, 11:12am
6
It was worth a try, this will require more research. This gem having been involved in lots of failed builds recently is suspicious.
merefield
(Robert)
January 11, 2024, 11:14am
7
Yeah, this is the current version:
~/discourse$ gem info rbtrace
*** LOCAL GEMS ***
rbtrace (0.5.1, 0.5.0, 0.4.14)
merefield
(Robert)
January 11, 2024, 11:16am
8
OK so I think rbtrace may be relying on the modernity of the background OS for some reason, see this advice:
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.
3 Likes
So is this the image, or the basse ubuntu that needs updating?
merefield
(Robert)
January 11, 2024, 11:18am
10
I read that as base Ubuntu.
For the record, what version are you on? (might help others)
2 Likes
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
merefield
(Robert)
January 11, 2024, 11:22am
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
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
merefield
(Robert)
January 11, 2024, 11:33am
14
Someone helpfully wrote a guide:
Hello all,
I have been using Docker with the Devicemapper storage driver. After manually editing the launcher script, I finally took the time to convert to Overlay2. Here are the instructions I took to do this. I hope this helps others. I see others have asked the question , but I don’t see any answers. I used this excellent guide to help figure this out.
Step 1: Halt your Discourse application (and other docker apps)
./launcher stop app
Step 2: Commit and save your old Docker containers/ima…
2 Likes
I took this advice, and am now back up and running. Thank you @merefield for your assistance.
1 Like
system
(system)
Closed
February 10, 2024, 2:40pm
16
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.