Upgrade Failed from v1.7.0.beta3 +20 TO 1.7.0.beta3

Support

AI 生成的摘要

User agung encountered an error while trying to upgrade from v1.7.0.beta3 +20 to 1.7.0.beta3, resulting in a “Killed” message during the compression process. agung shared screenshots of the issue and sought help.

jomaxro pointed out that the latest version is likely 1.7.0.beta3+20, making the downgrade unnecessary.

Steven suggested that the issue might be due to heavy memory usage and recommended checking the swap file size. He also advised running ./launcher rebuild app to recover from a killed upgrade.

After agung confirmed sufficient memory and swap space, they performed a server reboot, updated Docker, cleaned up, and rebuilt the app. Although they encountered another error, they were able to get Discourse back online after rebooting and rebuilding the app. agung thanked Steven and jomaxro for their assistance, marking the issue as solved.

1

HI

I’m trying to upgrade from v1.7.0.beta3 +20 TO 1.7.0.beta3

Got this error message

Compressing: application-5f751a6fe3e92d4cf1a5cb351c574378c5b0122f205342ab2a3895c8c45e394a.js
uglifyjs '/var/www/discourse/public/assets/_application-5f751a6fe3e92d4cf1a5cb351c574378c5b0122f205342ab2a3895c8c45e394a.js' -p relative -c -m -o '/var/www/discourse/public/assets/application-5f751a6fe3e92d4cf1a5cb351c574378c5b0122f205342ab2a3895c8c45e394a.js' --source-map-root '/assets' --source-map '/var/www/discourse/public/assets/application-5f751a6fe3e92d4cf1a5cb351c574378c5b0122f205342ab2a3895c8c45e394a.js.map' --source-map-url '/assets/application-5f751a6fe3e92d4cf1a5cb351c574378c5b0122f205342ab2a3895c8c45e394a.js.map'
Killed

Update :
Something strange happend after failed upgrade, here is the screenshot :

642×112 6.98 KB

After “click here to upgrade”

678×290 15.3 KB

Hope somebody can help

thank you

2

That’s strange, I’m fairly certain the latest tests_passed release is 1.7.0.beta3+20, as that’s what my instance is running…

3

It can happen if the memory usage is too heavy. You may want to check your swap file, make sure it’s big enough.

To have the latest version after a killed upgrade, use the console and do a ./launcher rebuild app

4

@Steven swap is ok, memory 63%. I’ll trying to do rebuild now

5

Update:

Rebooting server, do apt-get upgrade (apparently it upgrade docker-engine)

then doin launcher cleanup, rebuild app
got this error :

653×222 7.31 KB

Update:
After reboot & ./launcher rebuild app, discourse back online

SOLVED, Thanks @Steven, @jomaxro