Upgrading from Commits · discourse/discourse · GitHub to the latest has caused the site to go down, here is notable segments of the logs: I, [2022-02-15T05:27:48.995821 #1] INFO -- : Replacing (?-mix:^host.*all.*all.*127.*$) with host all all 0.0.0.0/0 md5 in /etc/postgresql/13/main/pg_hba.conf I,…

[이미지] balupton: It is the VC1S server from Scaleway You need to add some swap. Looks like you have plenty of disk, so you could add 2G or even 3G for safety. The discourse standard setup should, I think, have already set up the swap for you. Perhaps see Create a swapfile for your Linux serve…

There should be a more specific error above ‘FAILED’ if you scroll up. It looks like it doesn’t like a theme/component though. You may want to ./launcher restart app to bring back the pre-rebuild version so you can use the regular UI to disable the one in question before attempting another upgrade.…

[이미지] JammyDodger: Did scrolling up give you a clue as to which one? The only siginficant log from brew doctor was these: I, [2022-02-15T06:14:34.823778 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake themes:update assets:precompile' - Building - Building - buildi…

I can confirm this, I’ve tried this on 3 Different instances and builds are getting failed after reaching the below state. I, [2022-02-15T07:09:36.714521 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' I, [2022-02-15T07:09:46.598212 #1] INFO -- : I, [2022-02…

hey @balupton could you try changing EMBER_CLI_PROD_ASSETS: 0 and try rebuilding again? I have at least 1 successful rebuild after the above change.

These seem to be the only relevant logs that indicate anything is wrong: I, [2022-02-15T07:15:48.531001 #1] INFO -- : > cd /var/www/discourse && [ ! -d 'node_modules' ] || su discourse -c 'yarn install --production && yarn cache clean' warning Resolution field "lodash@4.17.21" is incompatible with…

Will try that, how do I apply it? Nevermind, found it: [이미지] New installs will default to Ember CLI builds in Production megaphoneAnnouncements As of today, all new self hosted installs of Discourse will default to using our Ember CLI builds in production. We…

Looking at the changelog: [이미지] Comparing 55007fbf5597e8d6c52464b93f519794bd9fb516...main · discourse/discourse A platform for community discussion. Free, open, simple. - Comparing 55007fbf5597e8d6c52464b93f519794bd9fb516...main · discourse/discourse I wonde…

[이미지] itsbhanusharma: exit code 137 Out of memory. Make sure you have enough (virtual) memory. 1GB of memory and 2GB of swap is probably too low nowadays for a rebuild.

Yep, it worked. vim /var/discourse/containers/app.yml env: # ... ## Workaround for: https://meta.discourse.org/t/failed-to-upgrade-discourse-instance-to-feb-15-2022/218204/7?u=balupton EMBER_CLI_PROD_ASSETS: 0

[이미지] RGJ: Make sure you have enough (virtual) memory. 1GB of memory and 2GB of swap is probably too low nowadays for a rebuild. with discourse now successfully running, top is currently returning: KiB Mem : **2041324** total, **287808** free, **1033300** used, **720216** buff/cache KiB Swap…

Failed to upgrade discourse instance to Feb 15 2022

지원 자체 호스팅

balupton (Benjamin Lupton) 2월 15, 2022, 7:54오전 7

Will try that, how do I apply it?

Nevermind, found it:

Will give it a go now.

글		댓글	조회수
Error while updating through launcher rebuild Self-hosting	2	620	4월 16, 2024
3.1.x to 3.2.0 upgrade hangs/fails on 1GB instance Self-hosting	34	1958	2월 23, 2024
I keep getting errors when updating Support	26	538	7월 16, 2025
Problem with Upgrade [error 137] Self-hosting server-resources	31	1723	2월 11, 2024
Discourse down. Updated certificate, rebuilt app, but still not working Self-hosting two-container	13	722	3월 22, 2024

Failed to upgrade discourse instance to Feb 15 2022

Related topics