Problem with Upgrade [error 137]

[Moin]

@anon36555649

only stable tested updates not the developer/beta ones

Did you read about the meaning of those?

Why does Discourse always install "beta" versions by default?

In Discourse, four primary release channels serve different purposes: main, tests-passed, beta, and stable. The default channel used when installing a production version of Discourse is tests-passed. Our nomenclature differs a bit from other software companies and will be explained here. main This channel represents the latest development version of Discourse. It contains the most recent features and improvements but may not be thoroughly tested and can be unstable, so it is not recommended…

From Discourse 3.2: adding -dev suffix to beta versions under active development

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. (hence, this is not an announcements topic) 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 ve…

[anon36555649]

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.

[anon36555649]

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

[Heliosurge (Dan DeMontmorency)]

@anon36555649

Have two standard install 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.

[Heliosurge (Dan DeMontmorency)]

@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)

[anon36555649]

@Heliosurge

edit App.yml to Stable

Don’t know how to do that either, what is YML?

[Moin]

Configure a supported tracking branch to get Discourse software updates

This guide describes how to change tracking branch for your Discourse instance, which determines how frequently updates are available to deploy and how you receive notifications about these updates. Supported branches tests-passed Tracking tests-passed is the recommended default to stay up to date with the bug fixes and remain compatible with the latest plugin versions. When a new commit is pushed the to the main branch, our build server automatically runs all our tes…

[anon36555649]

Followed those steps to set to stable but may have made a mistake with something, since now when attempting to rebuild again reports:

(<unknown>): 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.

[anon36555649]

Discourse Doctor reports that same error again and:

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.

[merefield (Robert)]

@anon36555649

YAML syntax error

Yup, you have. But this is a trivial issue. Just fix your syntax.

[anon36555649]

Am not sure what all is proper syntax, is there a way to reset to default or something?

Another report:

(<unknown>): 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.

[JammyDodger]

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.