I upgrade regularly (every month or so), and haven’t had an issue like this that prevented building. My server is currently inaccessible. I would say I have a pretty standard install . There is ample free disk space. discourse-doctor didn’t produce any errors or things that looked suspicious. Nothin…

I think error 137 is not enough memory. Did you do a standard install and let it add some swap when it gave you the option? There’s a pretty informative discussion about a similar error in this topic, if it sounds like it could be the case: [afbeelding] Failed to upgrade discourse…

Upgrade mislukt, "FAILED TO BOOTSTRAP", fout 137

Installatie

system (system) gesloten 11 november 2022 om 23:55 7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Topic		Antwoorden	Weergaven
Fail to upgrade - Make sure that `gem install json -v '1.8.2'` succeeds before bundling Installation server-resources	18	6718	14 februari 2015
Error while updating through launcher rebuild Installation	3	487	16 april 2024
Failed to boostrap (exit code 137) Installation server-resources	8	908	13 juni 2022
Failed to upgrade discourse instance to Feb 15 2022 Installation server-resources	30	2701	23 maart 2022
2.6.0 beta 3 update failed on disk and/or memory space Installation server-resources	29	2410	26 oktober 2020

Upgrade mislukt, "FAILED TO BOOTSTRAP", fout 137

Gerelateerde topics