For standard install site have this error log for most recent upgrade: ******************************************************** *** Please be patient, next steps might take a while *** ******************************************************** Cycling Unicorn, to free up memory Restarting unicorn pi…

[изображение] anon36555649: exit code 137 Out of memory. You’ll need to add swap or ram. But also you can try again and it might work. If you’re updating from the UX you should try a command line rebuild.

In console logged in as root, I type the command “apt upgrade” and this initiates the upgrade install. Thanks to @Arkshine for mentioning this here: [изображение] How to install updates with console installation Hello, For server updates, you can use apt upgrade with Ub…

Just to check, are you under the assumption that is upgrading your Discourse or your server?

Well had thought that did upgrade discourse, but perhaps that was the Ubuntu server instead that was being upgraded, not sure.

I think you may benefit from reading some more topics on the subject. If you have a search of the documentation , or just a search in general, I think you’ll find plenty of information that should help fill in the gaps in your knowledge. There is a substantial amount of advice that covers the basics …

[изображение] Jay Pfaffman: command line rebuild Missed that you wrote rebuild can rebuild the app. Here is the official guide: [изображение] Manually update Discourse and Docker image to latest sysadmin If you self-host Discourse, you occasionally need to run a m…

Because running the website (albeit with fewer Unicorns) + performing a build at the same time is costly in memory? I tried this out on my server (3 VCPU, 4GB): Online: 2.21 before upgrade → 1.7 as it frees up memory → 3.5 peak during build (GBs) Swap also went up ~200MB to peak ~800MB Command l…

[изображение] Robert: Because running the website (albeit with fewer Unicorns) + performing a build at the same time is costly in memory? That seems correct, no need for a question mark there! So rebuilding the app then automatically updates to most recent version it seems? [Screen Shot 20…

No, but you can slow things down by changing to stable. Unfortunately you just missed the boat this time as you can’t go backwards.

Ok, may want to change to that stable setting for only stable tested updates not the developer/beta ones. Looking to figure out how to do that.

Проблема с обновлением [error 137]

Поддержка Самостоятельное хостинг

anon36555649 01.Февраль.2024 00:24:39 16

Упустил, что вы написали, что пересборка может обновить приложение.

Вот официальное руководство:

Тема		Ответов	Просм.
I keep getting errors when updating Support	26	408	16.07.2025
2.6.0 beta 3 update failed on disk and/or memory space Self-hosting server-resources	29	2548	26.10.2020
Failed to upgrade discourse instance to Feb 15 2022 Self-hosting server-resources	30	2920	23.03.2022
Error while updating through launcher rebuild Self-hosting	3	556	16.04.2024
Upgrade failed, "FAILED TO BOOTSTRAP", error 137 Self-hosting server-resources	6	1051	11.11.2022

Проблема с обновлением [error 137]

Связанные темы