PSA: Stable 3.3.3 -> 3.4.0 upgrade via GUI failed, had to rebuild via command line

Installation
1

Just a heads-up for self-hosted stable branch users. For me the upgrade via the GUI failed, I’m not sure if this would happen to everyone, as I saw some errors about unicorn processes, which tends to be a random issue in my experience. But at any rate that left my forum in a state where it claimed to be up-to-date in /admin/update while still being stuck on the old version.

So I had to SSH into the server and /var/discourse/launcher rebuild app two times, the first time it just upgrades Postgres:

UPGRADE OF POSTGRES COMPLETE

Old 13 database is stored at /shared/postgres_data_old

To complete the upgrade, rebuild again using:

./launcher rebuild app

And the second time it finishes the rest of the upgrades.

After that was all over and verifying that my data was intact I also did a /var/discourse/launcher cleanup to get rid of the huge backup file that it created for the old database.

1 Like
2

AFAIK it will, and this is one of those upgrades that can’t be done using GUI.

2 Likes
3

It really shouldn’t allow people to try, but also, if you’re on Stable, I’d think it best to only do command line upgrades.

1 Like
4

This is what I was thinking too.

The GUI seems to work well enough for X.Y.z updates within a major Stable release, but yes, lesson learned for when there is a major new version.

2 Likes