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…

[image] 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.

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 …

[image] Jay Pfaffman: command line rebuild Missed that you wrote rebuild can rebuild the app. Here is the official guide: [image] Manually update Discourse and Docker image to latest Self-Hosting bookmark This guide provides step-by-step instructions f…

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…

[image] 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 2024-02-…

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.

[image] anon36555649: only stable tested updates not the developer/beta ones Did you read about the meaning of those? [image] Understanding Discourse release channels Site Management bookmark This guide explains the different types of Discourse releases …

Have read through those now, haven’t yet figured out how to change update settings for stable vs. main / beta / or tests-passed. Edit: Could be the answer is there isn’t a setting for this, maybe dev updates can only be done manually or something? Am just guessing don’t know.

Side note: During rebuild have notice that: 110:M 11 Feb 2024 04:26:05.828 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.…

Problem with Upgrade [error 137]

Support Self-hosting

Moin February 11, 2024, 5:43pm 27

Topic		Replies	Views
I keep getting errors when updating Support	26	427	July 16, 2025
2.6.0 beta 3 update failed on disk and/or memory space Self-hosting server-resources	28	2573	September 26, 2020
Failed to upgrade discourse instance to Feb 15 2022 Self-hosting server-resources	29	2943	February 16, 2022
Error while updating through launcher rebuild Self-hosting	2	563	April 16, 2024
Upgrade failed, "FAILED TO BOOTSTRAP", error 137 Self-hosting server-resources	5	1054	October 12, 2022

Problem with Upgrade [error 137]

Related topics