I did a bad thing. I inherited a discourse server for my organization. For months now, every time I log in, it has told me there are critical updates that must be installed (3.2.x → 3.3.x). I finally caved, and clicked on the updates in the admin panel. The docker update was fine - that finished fairly quickly, and everything was still working afterwards. Then I clicked on the 3.3 discourse update. It proceeded for a while, then threw up this error message: Bundle complete! 146 Gemfile dependencies, 185 gems now installed. Gems in the groups 'development' and 'test' were not installed. Bundled gems are installed into `./vendor/bundle` Post-install message from i18n: PSA: I18n will be dropping support for Ruby < 3.2 in the next major release (April 2025), due to Ruby's end of life for 3.1 and below (https://endoflife.date/ruby). Please upgrade to Ruby 3.2 or newer by April 2025 to continue using future versions of this gem. 1 installed gem you directly depend on is looking for funding. Run `bundle fund` for details $ yarn install yarn install v1.22.19 info No lockfile found. [1/5] Validating package.json... error discourse@: The engine "yarn" is incompatible with this module. Expected version "please-use-pnpm". Got "1.22.19" warning discourse@: The engine "pnpm" appears to be invalid. error Found incompatible module. info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. Docker Manager: FAILED TO UPGRADE # I had time to copy this, but when I hit the back button, it was apparent that the server is completely down. " Oops The software powering this discussion forum encountered an unexpected problem. We apologize for the inconvenience. Detailed information about the error was logged, and an automatic notification generated. We'll take a look at it. No further action is necessary. However, if the error condition persists, you can provide additional detail, including steps to reproduce the error, by posting a discussion topic in the site's feedback category." While I appreciate the reassurance here that it is being taken care of, I am fairly sure that I am the one who is supposed to be taking care of it. Suggestions on where to start?

Have you tried upgrading from the command line? [תמונה] Manually update Discourse and Docker image to latest Self-Hosting bookmark This guide provides step-by-step instructions for manually updating Discourse, the Docker container, and the Ubuntu operating system on a self-hosted setup. person_raising_hand Required user level: System Administrator warning SSH access to the server. If you self-host Discourse, you occasionally need to run a manual update via the command line to get the latest security releases and newest libraries. These updates are not picked up in admin/upgrade, which is why you’ll occa…

Can you please try a rebuild on the command line?

As suggested. Every now and then you will want to perform a command line update. Especially when the web interface fails. Most of the time a command line updates will resolve an update issue from the dashboard

התוכנה Discourse נשברה לאחר עדכון שנכשל

תמיכה

Adam_Price (Adam Price) 2 בנובמבר,‏ 2024,‏ 12:31am 5

Thanks everyone - a command line update and an increase in the virtual disk size did the trick.

We’re back online, with 3.4.

Phew.

נושא		תגובות	צפיות
Failed upgrade from 2.9.0.beta14 to 3.1.0.beta Self-hosting	10	1381	25 בינואר,‏ 2023
Problems with self-hosted upgrade to 3.x: cannot roll back Self-hosting	14	1445	28 בינואר,‏ 2023
Sorry, there was an error updating Discourse. Please check the logs below: Docker Manager: FAILED TO UPGRADE Self-hosting	1	299	18 במאי,‏ 2024
Failed to upgrade 3.1.0 Beta7 to 3.2.0 Beta3 as of 12/31/2023 Self-hosting	4	607	1 בינואר,‏ 2024
Error when upgrading Discourse Self-hosting	11	602	12 במאי,‏ 2025

התוכנה Discourse נשברה לאחר עדכון שנכשל

נושאים קשורים