SOLVED Can't start after update nodejs/npm

Mroczny

Hi, I have problem with Nodebb after nodejs and npm update.
I did stupid thing after update - used command npm audit fix --force.

System info:
OS: Debian 9
Nodebb: 1.17.1

./nodebb start logs:

NodeBB v1.17.1 Copyright (C) 2013-2014 NodeBB Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it under certain conditions.
For the full license, please visit: http://www.gnu.org/copyleft/gpl.html

Clustering enabled: Spinning up 3 process(es).

2021-06-09T19:46:31.228Z [8000/13807] - [32minfo[39m: Initializing NodeBB v1.17.1 https://umod.pl
2021-06-09T19:46:31.944Z [8000/13807] - [31merror[39m: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
    at validatePort (internal/validators.js:211:11)
    at lookupAndConnect (net.js:1000:5)
    at Socket.connect (net.js:976:5)
    at Object.connect (net.js:188:17)
    at /var/www/node_modules/ioredis/built/connectors/StandaloneConnector.js:58:45
    at processTicksAndRejections (internal/process/task_queues.js:77:11)
2021-06-09T19:46:31.954Z [8000/13807] - [31merror[39m: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
    at validatePort (internal/validators.js:211:11)
    at lookupAndConnect (net.js:1000:5)
    at Socket.connect (net.js:976:5)
    at Object.connect (net.js:188:17)
    at /var/www/node_modules/ioredis/built/connectors/StandaloneConnector.js:58:45
    at processTicksAndRejections (internal/process/task_queues.js:77:11)
2021-06-09T19:46:31.957Z [8000/13807] - [31merror[39m: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
    at validatePort (internal/validators.js:211:11)
    at lookupAndConnect (net.js:1000:5)
    at Socket.connect (net.js:976:5)
    at Object.connect (net.js:188:17)
    at /var/www/node_modules/ioredis/built/connectors/StandaloneConnector.js:58:45
    at processTicksAndRejections (internal/process/task_queues.js:77:11)
2021-06-09T19:46:31.961Z [8000/13807] - [31merror[39m: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
    at validatePort (internal/validators.js:211:11)
    at lookupAndConnect (net.js:1000:5)
    at Socket.connect (net.js:976:5)
    at Object.connect (net.js:188:17)
[cluster] Child Process (13807) has exited (code: 0, signal: null)
    at /var/www/node_modules/ioredis/built/connectors/StandaloneConnector.js:58:45
    at processTicksAndRejections (internal/process/task_queues.js:77:11)
2021-06-09T19:46:31.988Z [8002/13814] - [31merror[39m: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
2021-06-09T19:46:31.991Z [8001/13813] - [31merror[39m: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
    at validatePort (internal/validators.js:211:11)
    at validatePort (internal/validators.js:211:11)
[cluster] Child Process (13814) has exited (code: 0, signal: null)
    at lookupAndConnect (net.js:1000:5)
    at lookupAndConnect (net.js:1000:5)
[cluster] Child Process (13813) has exited (code: 0, signal: null)
    at Socket.connect (net.js:976:5)
    at Socket.connect (net.js:976:5)
    at Object.connect (net.js:188:17)
    at Object.connect (net.js:188:17)
    at /var/www/node_modules/ioredis/built/connectors/StandaloneConnector.js:58:45
    at /var/www/node_modules/ioredis/built/connectors/StandaloneConnector.js:58:45
    at processTicksAndRejections (internal/process/task_queues.js:77:11)
    at processTicksAndRejections (internal/process/task_queues.js:77:11)
2021-06-09T19:46:31.999Z [8002/13814] - [31merror[39m: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
2021-06-09T19:46:32.003Z [8001/13813] - [31merror[39m: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
    at validatePort (internal/validators.js:211:11)
    at validatePort (internal/validators.js:211:11)
    at lookupAndConnect (net.js:1000:5)
    at lookupAndConnect (net.js:1000:5)
    at Socket.connect (net.js:976:5)
    at Socket.connect (net.js:976:5)
    at Object.connect (net.js:188:17)
    at Object.connect (net.js:188:17)
    at /var/www/node_modules/ioredis/built/connectors/StandaloneConnector.js:58:45
    at /var/www/node_modules/ioredis/built/connectors/StandaloneConnector.js:58:45
    at processTicksAndRejections (internal/process/task_queues.js:77:11)
    at processTicksAndRejections (internal/process/task_queues.js:77:11)
2021-06-09T19:46:31.999Z [8002/13814] - [31merror[39m: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
2021-06-09T19:46:32.003Z [8001/13813] - [31merror[39m: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
    at validatePort (internal/validators.js:211:11)
    at validatePort (internal/validators.js:211:11)
    at lookupAndConnect (net.js:1000:5)
    at lookupAndConnect (net.js:1000:5)
    at Socket.connect (net.js:976:5)
    at Socket.connect (net.js:976:5)
    at Object.connect (net.js:188:17)
    at Object.connect (net.js:188:17)
    at /var/www/node_modules/ioredis/built/connectors/StandaloneConnector.js:58:45
    at /var/www/node_modules/ioredis/built/connectors/StandaloneConnector.js:58:45
    at processTicksAndRejections (internal/process/task_queues.js:77:11)
    at processTicksAndRejections (internal/process/task_queues.js:77:11)
2021-06-09T19:46:32.000Z [8002/13814] - [31merror[39m: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
2021-06-09T19:46:32.004Z [8001/13813] - [31merror[39m: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
    at validatePort (internal/validators.js:211:11)
    at validatePort (internal/validators.js:211:11)
    at lookupAndConnect (net.js:1000:5)
    at lookupAndConnect (net.js:1000:5)
    at Socket.connect (net.js:976:5)
    at Socket.connect (net.js:976:5)
    at Object.connect (net.js:188:17)
    at Object.connect (net.js:188:17)
    at /var/www/node_modules/ioredis/built/connectors/StandaloneConnector.js:58:45
    at /var/www/node_modules/ioredis/built/connectors/StandaloneConnector.js:58:45
    at processTicksAndRejections (internal/process/task_queues.js:77:11)
    at processTicksAndRejections (internal/process/task_queues.js:77:11)

Configuration:

{
    "url": "https://umod.pl",
    "secret": "x",
    "database": "redis",
    "redis": {
        "host": "",
        "port": "/home/redis/sock/redis.sock",
        "password": "x",
        "database": "0"
    },
    "port": ["8000", "8001", "8002"],
    "socket.io": {
    	"transports": ["websocket", "polling"],
    	"address": "https://umod.pl"
    }
}

I tried downgrade nodejs and npm using this commands:

npm install -g n
n 14.16.1

npm install -g npm@6.4.0

But still sewms not working.

./nodebb upgrade logs:

Thanks for help in advance.

Antosik

@mroczny said in Can't start after update nodejs/npm:

/home/redis/sock/redis.sock

Hi!
Try to specify the path to socket (in a redis section) in "host", not "port".

The config will be like this:

{
    "url": "https://umod.pl",
    "secret": "x",
    "database": "redis",
    "redis": {
        "host": "/home/redis/sock/redis.sock",
        "password": "x",
        "database": "0"
    },
    "port": ["8000", "8001", "8002"],
    "socket.io": {
    	"transports": ["websocket", "polling"],
    	"address": "https://umod.pl"
    }
}

Mroczny

@antosik Thanks now working properly!
In last update configuration file has been changed or update replaced this line?
Im asking because I didn't edit config.json

Antosik

@mroczny
No, in the previous update, a redis package was replaced via ioredis package. And that change is broke your configuration.
Related PR: https://github.com/NodeBB/NodeBB/pull/9545

pitaj created this issue in NodeBB/NodeBB

SOLVED Can't start after update nodejs/npm

closed fix(#9508): switch to ioredis #9545

Suggested Topics

Updated to v1.17.x, emoji stopped working?
Technical Support • error • • Teemberland

How to run a npm run script programatically
General Discussion • node.js nodejs script • • msinha

Anybody using ES6 yet?
General Discussion • es6 nodejs • • Julian Lam

Don't think my composer is working correctly.
Technical Support • composer • • tfraley

How can I print out a specific array entry in my template?
Technical Support • • wfsaxton

SOLVED Can't start after update nodejs/npm

closed fix(#9508): switch to ioredis #9545

Suggested Topics

Updated to v1.17.x, emoji stopped working? Technical Support • error • • Teemberland

How to run a npm run script programatically General Discussion • node.js nodejs script • • msinha

Anybody using ES6 yet? General Discussion • es6 nodejs • • Julian Lam

Don't think my composer is working correctly. Technical Support • composer • • tfraley

How can I print out a specific array entry in my template? Technical Support • • wfsaxton

Updated to v1.17.x, emoji stopped working?
Technical Support • error • • Teemberland

How to run a npm run script programatically
General Discussion • node.js nodejs script • • msinha

Anybody using ES6 yet?
General Discussion • es6 nodejs • • Julian Lam

Don't think my composer is working correctly.
Technical Support • composer • • tfraley

How can I print out a specific array entry in my template?
Technical Support • • wfsaxton