Today, I’ve tried to run an update and the rebuild keeps failing, I also removed all unofficial plugins, but I don’t know what to do further. This is the error message Location of failure: /usr/local/lib/ruby/gems/2.7.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn' exec failed with the p…

I’m not having any luck with a new build or getting the previous instance running yet, so since the weekend is coming up I may sit on this until next week in hopes that the situation can be fixed from the gem side …

Which procedure was this? I’m admittedly a bit confused now trying to follow the various ideas on this thread. Thanks!

The second part of this post: [image] Discourse update keeps failing Self-hosting If you’re using the Docker deployment method, you may have an older container which you can restart (check e.g. docker images and/or docker ps -a). You can also override the com…

I’ll give this a try. Thanks.

Another possible workaround is adding the following to the app.yml hooks: after_code: - exec: cmd: - sed -i -e 's/oj (3.13.*/oj (3.13.14)/' Gemfile.lock

I assume updates would still be unsafe after this, correct? Doing the build on the older commit currently.

[image] L30110: I assume updates would still be unsafe after this, correct? Correct, Discourse update keeps failing: Discourse will break again if you update after this, which is not ideal given the security update that has been released since (although exploitation potential seems pret…

Yeah. I was referring to the sed hook. OK, I see, in theory that would force the older gem version so updating would be OK. If the old commit build finishes (and it’s looking good so far), I may go back to the current commit and try that hook as a test. Build finished, let’s see if I’m back up …

Back up on old commit. Thanks all! Since I know that will work, I’ll rebuild on the current commit with the sed hook to test.

Build test with this failed. I may be specifying it incorrectly. Here’s the error: Pups::ExecError: sed -i -e 's/oj (3.13.*/oj (3.13.14)/' Gemfile.lock failed with return #<Process::Status: pid 222 exit 2> Location of failure: /usr/local/lib/ruby/gems/2.7.0/gems/pups-1.1.1/lib/pups/exec_command.rb:…

Discourse update keeps failing

Support Self-hosting

sam (Sam Saffron) July 15, 2022, 12:00am 69

I have this patched here:

https://github.com/discourse/discourse/pull/17505

It should land in our source tree within the next hour. Let me know if it works.

Topic		Replies	Views
Discourse update error Self-hosting	37	2192	March 1, 2023
Update Not Completed and Discourse not opening Self-hosting	17	524	July 17, 2024
Error while updating through launcher rebuild Self-hosting	3	559	April 16, 2024
Error upgrading Self-hosting	13	1646	October 20, 2016
Problem when updating Discourse Forum Self-hosting unsupported-install	20	2186	June 29, 2023

Discourse update keeps failing

Related topics