Hi, I just received an email from discourse, proposing to upgrade from 2.7.0.beta1 to 2.7.0.beta2. I went to the admin page and clicked on upgrade, and it seems like something has failed. As a result, it is not possible to access my dicourse instance anymore (Error 500). I include here the final …

Do you have any non standard plugins installed? You did a ./launcher rebuild app At the command line?

On my side, I dont have any non-standard plugins and I launched this on the command line. The first timeI was still getting the error. I then restarted my server, rebuilt the app… and it works.

Hi, thanks for the quick reply! I have a vanilla installation, never changed anything except for clicking on the “upgrade” button from time to time. This is why I considered what happened to my discourse instance to be very surprising. I didn’t try a ./launcher rebuild app, will try and report the…

My upgrade to 2.7.0.Beta2 cannot be even started - click on the one-click upgrade link in the email announcing this upgrade Hooray, a new version of Discourse is available! Your version: 2.7.0.beta1 New version: 2.7.0.beta2 Upgrade using our easy one-click browser upgrade See what’s new in th…

You’ll need to upgrade from the command line. There is a new docker base image. ./launcher rebuild app The announcement says that, but it’s not clear from the standard upgrade email.

I’ve just upgraded to 2.7.0.Beta2 You have to do this particular upgrade from the command line. cd /var/discourse git pull ./launcher rebuild app

My apologies for this asynchronous discussion - I started my question and had to suddenly leave my office. To prevent losing my unfinished message, I saved it - and it gave you the opportunity to answer my question before I fully posted it :wink:

The DO console would work if you don’t use a terminal. The buttons in the screenshot are initially disabled forcing you to upgrade Docker first. An aside:You could have left your reply as it saves automatically as a draft.

Spoke too soon Thanks, @geoff777 - it all makes sense now Trying to run cd /var/discourse git pull ./launcher rebuild app The rebuild app script failed two times in the row, at the precise same place: [image] This cannot be random networking interference. Please advise

In my case rebuild stucked at plugin discourse-vk-auth. Currently my instance works without this plugin. gem install rrule -v 0.4.2 -i /var/www/discourse/plugins/discourse-calendar/gems/2.7.2 --no-document --ignore-dependencies --no-user-install Successfully installed rrule-0.4.2 1 gem installed ge…

2.7.0.beta2 アップグレードに失敗しました

サポートインストール

geoff777 2021 年 1 月 22 日午後 4:14 7

2.7.0.Beta2 にアップグレードしました
この特定のアップグレードは、コマンドラインから実行する必要があります。

cd /var/discourse
git pull
./launcher rebuild app

「いいね！」 2

2.7.0.beta2 upgrade failed with ERROR: duplicate key

トピック		返信	表示
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	17	1965	2021 年 11 月 26 日
Latest site upgrade not working Self-hosting	11	1759	2022 年 2 月 22 日
An upgrade knocked my site offline; how long until it's restored? Self-hosting	16	325	2025 年 8 月 9 日
2.6.0 beta 3 update failed on disk and/or memory space Self-hosting server-resources	29	2483	2020 年 10 月 26 日
3.1.x to 3.2.0 upgrade hangs/fails on 1GB instance Self-hosting	34	1589	2024 年 2 月 23 日

2.7.0.beta2 アップグレードに失敗しました

関連トピック