Community

Can't start after update nodejs/npm

Solved Technical Support
  • MrocznyM

    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] - info: Initializing NodeBB v1.17.1 https://umod.pl
2021-06-09T19:46:31.944Z [8000/13807] - error: 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] - error: 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] - error: 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] - error: 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] - error: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
2021-06-09T19:46:31.991Z [8001/13813] - error: 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] - error: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
2021-06-09T19:46:32.003Z [8001/13813] - error: 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] - error: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
2021-06-09T19:46:32.003Z [8001/13813] - error: 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] - error: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.
2021-06-09T19:46:32.004Z [8001/13813] - error: 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 [email protected]

    But still sewms not working.

    ./nodebb upgrade logs:
    d748f99a-3643-44d3-a904-67b99bc7cdda-image.png

    Thanks for help in advance. 🙂

    AntosikA 1 Reply
    0
  • AntosikA

    @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"
    }
}
    MrocznyM 1 Reply
    1
  • MrocznyM

    @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

    AntosikA 1 Reply
    0
  • AntosikA

    @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

    1

Suggested Topics

  • Macrow WillsonM

    Can't find SSO settings

    Technical Support
    0 Votes
    2 Posts
    510 Views

    Macrow WillsonM

    found it:

    needs ./nodebb build needs to open dev console to flush cache
  • TelokisT

    [Module] Amie: Amalgamation Made Insanely Easy!

    General Discussion
    0 Votes
    6 Posts
    2478 Views

    TelokisT

    @Bri Yes there are solutions like Microsoft's vcpkg or even cppan.

    But my tool would be more like a deployment complement: you would generate your binaries for the end user to download them but also an amalgamated version in case they want to use the quick n easy way.

    One thing I'd like to setup if this happens to be successful would be a cloud service which would allow to easily amalgamate your project.

  • C

    Ubuntu 16.04 executing '/path/to/nodebb start' causes error

    Technical Support
    0 Votes
    4 Posts
    1241 Views

    C

    @PitaJ Worked, thanks 🙂 For some reason I had the idea cd wouldn't work there

  • K

    Node js process.nextTick doesn't work properly

    NodeBB Development
    0 Votes
    1 Posts
    1602 Views

    K

    Well, I have this issue that I need to do following things:
    1.Mongo Find
    2. Foreach
    3. MongoFind
    4 one more Foreach.

    because of asynchronaus mongo calls it is difficult to get proper result, however process.nextTick should handle this problem and still I have problem:

    function find(dbComm) {

    dbComm.forEach(function (current) { id= parseFloat(current.ID); db.anotherCollection.find({ ID: id}, function (error, result) { result.forEach(function (rank) { if (parseFloat(result.ID) == parseFloat(current.ID)) { rank.rank = 'Some calculations'; } }); }); });

    }

    app.get('/someparams', function (req, res) {

    db.collection.find().sort({ "rank": order }).skip(pagenumber).limit(5, function (err, result) { process.nextTick(function () { find(result, function () { }) }); process.nextTick(function () { res.send(result); }); });

    And on client side I should recive an array where the rank equals 'Some Calculations'
    but unfortunetly it is not...
    However...! If I add setTimeout(function(){}) before res.send(result) (and res.send(result) will be placed inside setTimeout) it actually does work and on client side I recive data with "Some Calculations" but it is just timeout and it fails sometimes and client dont recive "Some Calculations"
    if I put process.nextTick instead of setTimeout it doesnt work and "Some calc..." are not sent.

    Something is beeing done eralier then it should (probably in forEach in find() function)
    and my question is how to deal with it? maybe I should put process.nextTick in different function ?

  • X

    NodeJS Help [Anyone that could help me]

    General Discussion
    0 Votes
    4 Posts
    2059 Views

    debianmasterD

    test tst test

| | | |
Copyright © 2023 NodeBB | Contributors