I started upgrading through the Web interface, first docker, which went fine, and then the main Discourse upgrade to beta8. That seems to have gotten stuck (for 30+ minutes, with no change) in a “compressing” phase. [39%20AM] The site seems to still be working mostly, although I couldn’t get to a private message. I’m planning to click Reset Upgrade unless someone says not to right away. :slight_smile: Here are the last two lines of the log: Compressing: locales/sr-53d537749608d7dfdfcd3a2581d2afb1dfa2447813239a81a56398a9e6b6e5e6.js uglifyjs '/var/www/discourse/public/assets/locales/_sr-53d537749608d7dfdfcd3a2581d2afb1dfa2447813239a81a56398a9e6b6e5e6.js' -p relative -c -m -o '/var/www/discourse/public/assets/locales/sr-53d537749608d7dfdfcd3a2581d2afb1dfa2447813239a81a56398a9e6b6e5e6.js' --source-map-root '/assets/locales' --source-map '/var/www/discourse/public/assets/locales/sr-53d537749608d7dfdfcd3a2581d2afb1dfa2447813239a81a56398a9e6b6e5e6.js.map' --source-map-url '/assets/locales/sr-53d537749608d7dfdfcd3a2581d2afb1dfa2447813239a81a56398a9e6b6e5e6.js.map' gzip -f -c -9 /var/www/discourse/public/assets/locales/sr-53d537749608d7dfdfcd3a2581d2afb1dfa2447813239a81a56398a9e6b6e5e6.js > /var/www/discourse/public/assets/locales/sr-53d537749608d7dfdfcd3a2581d2afb1dfa2447813239a81a56398a9e6b6e5e6.js.gz Compressing: application-925ac82337cd3f887f7ac5a86e5cb6081076cf526ae4d0c8ae77c2a8596f7aa7.js uglifyjs '/var/www/discourse/public/assets/_application-925ac82337cd3f887f7ac5a86e5cb6081076cf526ae4d0c8ae77c2a8596f7aa7.js' -p relative -c -m -o '/var/www/discourse/public/assets/application-925ac82337cd3f887f7ac5a86e5cb6081076cf526ae4d0c8ae77c2a8596f7aa7.js' --source-map-root '/assets' --source-map '/var/www/discourse/public/assets/application-925ac82337cd3f887f7ac5a86e5cb6081076cf526ae4d0c8ae77c2a8596f7aa7.js.map' --source-map-url '/assets/application-925ac82337cd3f887f7ac5a86e5cb6081076cf526ae4d0c8ae77c2a8596f7aa7.js.map'

OK, I guess Reset Upgrade may not be what I should do. Suggestions about how to get past this stuck upgrade? [20%20AM]

Have you tried running ./launcher app rebuild in a terminal?

No, since I’ve only dealt with Discourse at the interface level so far and would have to get my developer to do that. If that’s the fix, I’ll get him do that. Also, I just wanted to make sure the developers knew that the install was failing, since it might be indicative of some bug. I have the log of the install so far saved out.

[image] adamengst: No, since I’ve only dealt with Discourse at the interface level so far and would have to get my developer to do that. If that’s the fix, I’ll get him do that. Ya, it sounds like there isn’t much more you can do through the admin interface.

And indeed updating through the command line worked fine. So the devs should just consider this an anecdotal bug report with the beta8 installer.

I don’t see a bug here. Asset bundling is the most CPU intensive step in the upgrade process. Depending on your CPU it can take a couple of hours to finish…

It never progressed from the point where it stopped, despite running for 4 more hours. Which seems wrong.

Chiming in here that we are stuck as well on the discourse v2.3.0.beta3 +20 update. I am seeing this; New Version Available! Remote Version: v2.3.0.beta9 +48 Last Updated: 9 hours ago 926 new commits With a blue box and ‘Currently Upgrading…’ It’s been like this for weeks.

Beta8 upgrade stuck halfway

Product Support

codinghorror (Jeff Atwood) April 28, 2019, 7:55am 10

I suggest SSH-ing in and updating at the command prompt.

cd /var/discourse
./launcher rebuild app

Topic		Replies	Views
Where is the upgrade button Product Support	9	1607	November 29, 2016
Upgraded but admin page says out of date Product Support	21	3041	May 12, 2015
Upgrade link no longer works Self-hosting	7	1178	November 22, 2021
Upgrade Failed from v1.7.0.beta3 +20 TO 1.7.0.beta3 Product Support	4	1063	August 29, 2016
Discourse thinks it is upgrading but it is not Product Support	6	2673	July 2, 2016

Beta8 upgrade stuck halfway

Related topics