# Problem with Upgrade \[error 137\]
**URL:** https://meta.discourse.org/t/problem-with-upgrade-error-137/293652
**Category:** Self-hosting
**Tags:** server-resources
**Created:** [January 31, 2024, 4:33pm UTC](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652 "2024-01-31T16:33:52Z")
**Posts on this page:** 13
**Page:** 2
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [February 2, 2024, 12:59am UTC](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652/21 "2024-02-02T00:59:34Z")
> [@anon36555649](#):
>
> only stable tested updates not the developer/beta ones
Did you read about the meaning of those?
> [@Understanding Discourse release channels](https://meta.discourse.org/t/why-does-discourse-always-install-beta-versions-by-default/264400):
>
> bookmark This guide explains the different types of Discourse releases and how different channels are used for updates. person_raising_hand Required user level: All users Release channels Discourse has four primary release channels, each serving a different purpose: main, latest, release, and esr. The default channel used when installing a production version of Discourse is latest. Since November 2025, Discourse uses a date-based versioning scheme: YYYY.MM.PATCH (e.g., v2026.2.0). On …
> [@From Discourse 3.2: adding -dev suffix to beta versions under active development](https://meta.discourse.org/t/from-discourse-3-2-adding-dev-suffix-to-beta-versions-under-active-development/273490):
>
> On tests-passed, starting with 3.2.0.beta1-dev, Discourse core version numbers will include a -dev suffix to indicate that they’re not the final ‘release’ versions of a beta. This suffix doesn’t appear in the UI, so this is a technicality which will have no impact on the vast majority of people. For the technical details, see below: In the beta series for Discourse 3.1 and below, our versioning strategy was to ‘release’ a beta, and then leave the version number in tests-passed exactly the sam…
---
### Author:  [@anon36555649](https://meta.discourse.org/u/anon36555649)
#### Post date: [February 2, 2024, 4:46am UTC](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652/22 "2024-02-02T04:46:44Z")
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.
---
### Author:  [@anon36555649](https://meta.discourse.org/u/anon36555649)
#### Post date: [February 11, 2024, 4:43am UTC](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652/23 "2024-02-11T04:43:11Z")
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.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.`
Not sure how to do this, how is this done does anyone know?:
`add 'vm.overcommit_memory = 1' to /etc/sysctl.conf`
---
### Author:  [@Heliosurge](https://meta.discourse.org/u/Heliosurge)
#### Post date: [February 11, 2024, 7:22am UTC](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652/24 "2024-02-11T07:22:21Z")
> [@anon36555649](#):
>
> Have two [standard install](https://meta.discourse.org/t/142537?silent=true) sites on digital ocean total cost for both of these is $16.32 a month, this is a lot less that paying the $100 a month for one standard hosted site but so far haven’t had any sign ups for those so this is a waste unless people want to join there may shut those sites down
Getting folks to Join up and be active is often a challenge. You need to seed content & discussions. Friends & Family can help. But you may also want to consider promoting your site in other social media platforms.
---
### Author:  [@Heliosurge](https://meta.discourse.org/u/Heliosurge)
#### Post date: [February 11, 2024, 7:26am UTC](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652/25 "2024-02-11T07:26:22Z")
> [@anon36555649](#):
>
> Have read through those now, haven’t yet figured out how to change update settings for stable vs. main / beta / or tests-passed.
This is a line in your app.yml
Best to stick with Test-passed. If on Test-passed if you wanted to switch to stable you would need to pause upgrading until stable reaches Test-passed version number. Then edit App.yml to Stable(or what it says in the app.yml comment)
---
### Author:  [@anon36555649](https://meta.discourse.org/u/anon36555649)
#### Post date: [February 11, 2024, 5:06pm UTC](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652/26 "2024-02-11T17:06:40Z")
> [@Heliosurge](#):
>
> edit App.yml to Stable
Don’t know how to do that either, what is YML?
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [February 11, 2024, 5:43pm UTC](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652/27 "2024-02-11T17:43:55Z")
> [@Configure a supported tracking branch to get Discourse software updates](https://meta.discourse.org/t/configure-a-supported-tracking-branch-to-get-discourse-software-updates/17014):
>
> bookmark This guide explains how to configure a supported tracking branch for your Discourse instance to manage software updates. person_raising_hand Required user level: System Administrator warning Console access is required. Managing your Discourse instance’s tracking branch determines the frequency and type of updates you receive. This guide explains the different tracking branches available and provides a step-by-step approach to changing the branch on your setup. Summary Disco…
---
### Author:  [@anon36555649](https://meta.discourse.org/u/anon36555649)
#### Post date: [February 11, 2024, 9:20pm UTC](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652/28 "2024-02-11T21:20:43Z")
Followed those steps to set to stable but may have made a mistake with something, since now when attempting to rebuild again reports:
```plaintext
(): could not find expected ':' while scanning a simple key at line 113 column 1 -e LANG=en_US.UTF-8
YAML syntax error. Please check your containers/*.yml config files.
```
---
### Author:  [@anon36555649](https://meta.discourse.org/u/anon36555649)
#### Post date: [February 11, 2024, 9:33pm UTC](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652/29 "2024-02-11T21:33:12Z")
Discourse Doctor reports that same error again and:
```plaintext
starting up existing container
+ /usr/bin/docker start app
Error response from daemon: driver failed programming external connectivity on endpoint app (f3856e49bfe229cf43f040aca909076ea3dadd512282ec333ae67122d327e638): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use
Error: failed to start containers: app
Failed to restart the container.
```
Darn, maybe would be a good idea to start over with this one.
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [February 11, 2024, 9:37pm UTC](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652/30 "2024-02-11T21:37:40Z")
> [@anon36555649](#):
>
> `YAML syntax error`
Yup, you have. But this is a trivial issue. Just fix your syntax.
---
### Author:  [@anon36555649](https://meta.discourse.org/u/anon36555649)
#### Post date: [February 11, 2024, 9:46pm UTC](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652/31 "2024-02-11T21:46:22Z")
Am not sure what all is proper syntax, is there a way to reset to default or something?
Another report:
```plaintext
(): block sequence entries are not allowed in this context at line 18 column 39 -e LANG=en_US.UTF-8
YAML syntax error. Please check your containers/*.yml config files.
```
Edit: seems to be corrected now rebuild is working.
Set one site to stable updates will set other one to main recent developer updates.
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [February 11, 2024, 10:22pm UTC](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652/32 "2024-02-11T22:22:41Z")
I think this has strayed quite far beyond the original question. Let’s close this off now it’s solved and you can start a new topic on installing a stable version. 🙂
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [February 11, 2024, 10:22pm UTC](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652/33 "2024-02-11T22:22:44Z")
[Previous page](https://meta.discourse.org/t/problem-with-upgrade-error-137/293652.md?page=1)