# Beta8 升级卡在半途
**URL:** https://meta.discourse.org/t/beta8-upgrade-stuck-halfway/86762
**Category:** Support
**Created:** [2018年五月4日 14:26 UTC](https://meta.discourse.org/t/beta8-upgrade-stuck-halfway/86762 "2018-05-04T14:26:32Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@adamengst](https://meta.discourse.org/u/adamengst)
#### Post date: [2018年五月4日 14:26 UTC](https://meta.discourse.org/t/beta8-upgrade-stuck-halfway/86762/1 "2018-05-04T14:26:32Z")
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.
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. 🙂
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'
```
---
### Author:  [@adamengst](https://meta.discourse.org/u/adamengst)
#### Post date: [2018年五月4日 15:28 UTC](https://meta.discourse.org/t/beta8-upgrade-stuck-halfway/86762/2 "2018-05-04T15:28:14Z")
OK, I guess Reset Upgrade may not be what I should do. Suggestions about how to get past this stuck upgrade?
---
### Author:  [@Denis\_Heraud](https://meta.discourse.org/u/Denis_Heraud)
#### Post date: [2018年五月4日 15:36 UTC](https://meta.discourse.org/t/beta8-upgrade-stuck-halfway/86762/3 "2018-05-04T15:36:03Z")
Have you tried running ./launcher app rebuild in a terminal?
---
### Author:  [@adamengst](https://meta.discourse.org/u/adamengst)
#### Post date: [2018年五月4日 18:37 UTC](https://meta.discourse.org/t/beta8-upgrade-stuck-halfway/86762/4 "2018-05-04T18:37:12Z")
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.
---
### Author:  [@Denis\_Heraud](https://meta.discourse.org/u/Denis_Heraud)
#### Post date: [2018年五月4日 18:53 UTC](https://meta.discourse.org/t/beta8-upgrade-stuck-halfway/86762/5 "2018-05-04T18:53:37Z")
> [@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.
---
### Author:  [@adamengst](https://meta.discourse.org/u/adamengst)
#### Post date: [2018年五月4日 21:26 UTC](https://meta.discourse.org/t/beta8-upgrade-stuck-halfway/86762/6 "2018-05-04T21:26:09Z")
And indeed updating through the command line worked fine. So the devs should just consider this an anecdotal bug report with the beta8 installer.
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [2018年五月4日 23:56 UTC](https://meta.discourse.org/t/beta8-upgrade-stuck-halfway/86762/7 "2018-05-04T23:56:36Z")
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…
---
### Author:  [@adamengst](https://meta.discourse.org/u/adamengst)
#### Post date: [2018年五月5日 14:48 UTC](https://meta.discourse.org/t/beta8-upgrade-stuck-halfway/86762/8 "2018-05-05T14:48:52Z")
It never progressed from the point where it stopped, despite running for 4 more hours. Which seems wrong.
---
### Author:  [@sarafina](https://meta.discourse.org/u/sarafina)
#### Post date: [2019年四月27日 21:11 UTC](https://meta.discourse.org/t/beta8-upgrade-stuck-halfway/86762/9 "2019-04-27T21:11:54Z")
Chiming in here that we are stuck as well on the [
discourse](https://github.com/discourse/discourse.git) 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](https://github.com/discourse/discourse/compare/079b0f4...de79313)
With a blue box and ‘Currently Upgrading…’
It’s been like this for weeks.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2019年四月28日 07:55 UTC](https://meta.discourse.org/t/beta8-upgrade-stuck-halfway/86762/10 "2019-04-28T07:55:13Z")
I suggest SSH-ing in and updating at the command prompt.
`cd /var/discourse`
`./launcher rebuild app`
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [2022年八月9日 21:04 UTC](https://meta.discourse.org/t/beta8-upgrade-stuck-halfway/86762/12 "2022-08-09T21:04:10Z")