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: [image] Failed to upgrade discourse inst…

Upgrade failed, "FAILED TO BOOTSTRAP", error 137

Installation

system (system) Closed November 11, 2022, 11:55pm 7

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

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

Upgrade failed, "FAILED TO BOOTSTRAP", error 137

Related topics