Warnings on upgrade to 2.9.0.beta1

Product Support Self-hosting

AI-generated summary

The discussion revolves around warnings encountered during an upgrade to Discourse 2.9.0.beta1. Initially, Jonathan5 shared a list of warnings and asked if they were anything to worry about. RGJ reassured that most warnings are harmless, with the exception of one related to a TCP listening socket.

RGJ also clarified that the warning about Node.js version is incorrect, as Node v16.13.2 is indeed the “Active LTS” version.

To verify if everything works after the upgrade, RGJ suggested checking that the forum appears normally, logging in, uploading an image, and sending an email. Jonathan5 confirmed that these functions work.

Additionally, Ed_S shared their experience with setting vm.overcommit_memory=1 in /etc/sysctl.conf to address the overcommit_memory warning, which may be relevant for installations with limited RAM.

1

Are any of these anything to worry about? I think I’ve seen some of them before, and suspect that the answer is No, though it would be good to hear that :slight_smile: Thanks.

103:M 10 Feb 2022 14:23:47.564 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 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.

131:M 10 Feb 2022 14:23:57.845 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use

I, [2022-02-10T14:25:16.626751 #1]  INFO -- : > cd /var/www/discourse && [ ! -d 'node_modules' ] || su discourse -c 'yarn install --production && yarn cache clean'
warning Resolution field "lodash@4.17.21" is incompatible with requested version "lodash@4.17.15"
warning " > @mixer/parallel-prettier@2.0.1" has unmet peer dependency "prettier@^2.0.0".
I, [2022-02-10T14:26:46.311554 #1]  INFO -- : yarn install v1.22.17

W, [2022-02-10T14:27:19.491563 #1167]  WARN -- : Removed sourceMappingURL comment for missing asset '/popper.js.map' from /var/www/discourse/vendor/assets/javascripts/popper.js

[WARN] (broccoli-terser-sourcemap) Minifying "assets/discourse.js" took: 22025ms (more than 20,000ms)
[WARN] (broccoli-terser-sourcemap) "chunk.0.b5c6b3de0b67131d0851.js.map;", "chunk.2.bf34ae0559b62d8d3c24.js.map//#" referenced in "assets/vendor.js" could not be found

WARNING: Node v16.13.2 is not tested against Ember CLI on your platform. We recommend that you use the most-recent "Active LTS" version of Node.js. See https://git.io/v7S5n for details.
DEPRECATION: The integration of jQuery into Ember has been deprecated and will be removed with Ember 4.0. You can either opt-out of using jQuery, or install the `@ember/jquery` addon to provide the jQuery integration. Please consult the deprecation guide for further details: https://emberjs.com/deprecations/v3.x#toc_jquery-apis
2

Only this one is slightly worrying but if everything works then I would ignore it.

Could not create server TCP listening socket *:6379: bind: Address already in use

All the others are harmless.

But… but… Node v16 is the “active LTS” version of Node.

3

Thanks for the quick reply! I’m not in a position to check whether everything works :slight_smile: What’s the minimum you’d be looking for – just that the forum appears on screen as normal?

4

I would at least try logging in, uploading an image and sending an email.

5

Those things work. Thanks :slight_smile:

6

I notice that in both my installations (both have just 1G of RAM and 2G of swap) I have at some point followed that advice and set up vm.overcommit_memory=1 in /etc/sysctl.conf.