Solved Forum down after restart

  • So it works of you run with node app, right? No errors when you run that?

    Have you double checked to make sure all node processes are killed?

    If you're running with a single port, you might try using screen or tmux to run with node app as a stopgap. That essentially the same as running with ./nodebb dev except all security checks stay in place.

    You could also try setting "daemon": false in config.json and try ./nodebb start with that.

    As for permissions, yeah make sure all files are owned by nodebb:nodebb and have 755 permissions.

  • @pitaj a bit of a positive development. I've added "daemon": false into config.json and have successfully started NodeBB. However, this then runs as a session which isn't great, but I can at least close the terminal window and the process continues to run without dying.

    For now, this should be enough to keep the forum running until I figure out exactly why it won't start as a daemon. I noticed there's an upgrade to core so I'll try that also (1.18.3)

  • @phenomlab Quite the saga here. Bummer for sure, especially on a production box. What prompted the restart? Perchance did that follow any system updates? If so, I presume you're hip enough to have already considered such but just a thought.

    Royal pita but maybe time to cut your losses, export the db whilst you can, spin up a new vm and go from there? Tough call.

  • GNU/Linux Gamers

    What if you set up a new NodeBB from scratch but use the same database in your config and then move the uploads folder to the new one too?
    Meaning all plugins and stuff like that will be nonexistant and it will be stock nodeBB installation. Then, you can reinstall your plugins one by one and your custom things too to see what exactly is causing this problem

    Also i just read the latest post that you have (somewhat) fixed the issue but if your feeling up to a tedious job (lol) then try my solution

  • @baris @PitaJ just tried an upgrade, and got this

    Welcome to Ubuntu 20.04.3 LTS (GNU/Linux 5.13.7-051307-lowlatency x86_64)
     * Documentation:
     * Management:
     * Support:
    Last login: Thu Sep 23 19:49:08 2021 from
    [email protected]:~$ cd nodebb
    [email protected]:~/nodebb$ git fetch
    remote: Enumerating objects: 767, done.
    remote: Counting objects: 100% (607/607), done.
    remote: Compressing objects: 100% (91/91), done.
    remote: Total 767 (delta 535), reused 580 (delta 516), pack-reused 160
    Receiving objects: 100% (767/767), 196.89 KiB | 12.30 MiB/s, done.
    Resolving deltas: 100% (576/576), completed with 254 local objects.
     * [new branch]          dependabot/npm_and_yarn/install/commander-8.2.0         -> origin/dependabot/npm_and_yarn/install/commander-8.2.0
     + e0fda82b2...7502d5da8 dependabot/npm_and_yarn/install/connect-pg-simple-7.0.0 -> origin/dependabot/npm_and_yarn/install/connect-pg-simple-7.0.0  (forced update)
     * [new branch]          dependabot/npm_and_yarn/install/mongodb-4.1.2           -> origin/dependabot/npm_and_yarn/install/mongodb-4.1.2
     + b0787b593...a8ba14cdc dependabot/npm_and_yarn/install/postcss-clean-1.2.2     -> origin/dependabot/npm_and_yarn/install/postcss-clean-1.2.2  (forced update)
       0a56158bb..04ee5c0df  master                                                  -> origin/master
     + 4a5f10d2a...b638183dd renovate/mongodb-4.x                                    -> origin/renovate/mongodb-4.x  (forced update)
     * [new branch]          topic-linkbacks                                         -> origin/topic-linkbacks
       9410a73aa..1fad6f680  v1.17.x                                                 -> origin/v1.17.x
       854c078b7..9e5223697  v1.18.x                                                 -> origin/v1.18.x
     * [new tag]             v1.17.2-beta.8                                          -> v1.17.2-beta.8
     * [new tag]             v1.18.3                                                 -> v1.18.3
     * [new tag]             v1.17.2-beta.3                                          -> v1.17.2-beta.3
     * [new tag]             v1.17.2-beta.4                                          -> v1.17.2-beta.4
     * [new tag]             v1.17.2-beta.5                                          -> v1.17.2-beta.5
     * [new tag]             v1.17.2-beta.6                                          -> v1.17.2-beta.6
     * [new tag]             v1.17.2-beta.7                                          -> v1.17.2-beta.7
    [email protected]:~/nodebb$ git reset --hard origin/v1.18.x
    HEAD is now at 9e5223697 chore: incrementing version number - v1.18.3
    [email protected]:~/nodebb$ ./nodebb upgrade
    Updating NodeBB...
    1. Updating package.json file with defaults...  OK
    2. Bringing base dependencies up to date...  started
    npm ERR! code ERESOLVE
    npm ERR! ERESOLVE unable to resolve dependency tree
    npm ERR! 
    npm ERR! While resolving: [email protected]
    npm ERR! Found: [email protected]
    npm ERR! node_modules/mongodb
    npm ERR!   [email protected]"3.7.1" from the root project
    npm ERR! 
    npm ERR! Could not resolve dependency:
    npm ERR! peer [email protected]"^4.1.0" from [email protected]
    npm ERR! node_modules/connect-mongo
    npm ERR!   [email protected]"4.6.0" from the root project
    npm ERR! 
    npm ERR! Fix the upstream dependency conflict, or retry
    npm ERR! this command with --force, or --legacy-peer-deps
    npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
    npm ERR! 
    npm ERR! See /home/sudonix/.npm/eresolve-report.txt for a full report.
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /home/sudonix/.npm/_logs/2021-09-23T18_51_40_851Z-debug.log
    Error installing dependencies!
    message: Command failed: npm install --production
    stdout: null
    stderr: null
    Error occurred during upgrade: Error: Command failed: npm install --production
        at checkExecSyncError (node:child_process:826:11)
        at Object.execSync (node:child_process:900:15)
        at Object.installAll (/home/sudonix/nodebb/src/cli/package-install.js:73:9)
        at Object.handler (/home/sudonix/nodebb/src/cli/upgrade.js:21:19)
        at runSteps (/home/sudonix/nodebb/src/cli/upgrade.js:54:16)
        at processTicksAndRejections (node:internal/process/task_queues:96:5)
        at async Object.runUpgrade [as upgrade] (/home/sudonix/nodebb/src/cli/upgrade.js:84:3)
    2021-09-23T18:51:40.893Z [4567/78126] - error: uncaughtException: Command failed: npm install --production
    Error: Command failed: npm install --production
        at checkExecSyncError (node:child_process:826:11)
        at Object.execSync (node:child_process:900:15)
        at Object.installAll (/home/sudonix/nodebb/src/cli/package-install.js:73:9)
        at Object.handler (/home/sudonix/nodebb/src/cli/upgrade.js:21:19)
        at runSteps (/home/sudonix/nodebb/src/cli/upgrade.js:54:16)
        at processTicksAndRejections (node:internal/process/task_queues:96:5)
        at async Object.runUpgrade [as upgrade] (/home/sudonix/nodebb/src/cli/upgrade.js:84:3) {"error":{"status":1,"signal":null,"output":[null,null,null],"pid":78133,"stdout":null,"stderr":null},"stack":"Error: Command failed: npm install --production\n    at checkExecSyncError (node:child_process:826:11)\n    at Object.execSync (node:child_process:900:15)\n    at Object.installAll (/home/sudonix/nodebb/src/cli/package-install.js:73:9)\n    at Object.handler (/home/sudonix/nodebb/src/cli/upgrade.js:21:19)\n    at runSteps (/home/sudonix/nodebb/src/cli/upgrade.js:54:16)\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)\n    at async Object.runUpgrade [as upgrade] (/home/sudonix/nodebb/src/cli/upgrade.js:84:3)","exception":true,"date":"Thu Sep 23 2021 19:51:40 GMT+0100 (British Summer Time)","process":{"pid":78126,"uid":1021,"gid":1011,"cwd":"/home/sudonix/nodebb","execPath":"/usr/bin/node","version":"v16.10.0","argv":["/usr/bin/node","/home/sudonix/nodebb/nodebb","upgrade"],"memoryUsage":{"rss":67944448,"heapTotal":31772672,"heapUsed":21097072,"external":1831674,"arrayBuffers":926654}},"os":{"loadavg":[0.27,0.12,0.03],"uptime":85792.33},"tr:ace":[{"column":11,"file":"node:child_process","function":"checkExecSyncError","line":826,"method":null,"native":false},{"column":15,"file":"node:child_process","function":"Object.execSync","line":900,"method":"execSync","native":false},{"column":9,"file":"/home/sudonix/nodebb/src/cli/package-install.js","function":"Object.installAll","line":73,"method":"installAll","native":false},{"column":19,"file":"/home/sudonix/nodebb/src/cli/upgrade.js","function":"Object.handler","line":21,"method":"handler","native":false},{"column":16,"file":"/home/sudonix/nodebb/src/cli/upgrade.js","function":"runSteps","line":54,"method":null,"native":false},{"column":5,"file":"node:internal/process/task_queues","function":"processTicksAndRejections","line":96,"method":null,"native":false},{"column":3,"file":"/home/sudonix/nodebb/src/cli/upgrade.js","function":"async Object.runUpgrade [as upgrade]","line":84,"method":"runUpgrade [as upgrade]","native":false}]}
    [email protected]:~/nodebb$ 


    Any thoughts ?


  • @baris thanks

  • @baris @pitaj after upgrading to 1.18.3 I now get this when attempting to start NodeBB (as daemon)

        at processTicksAndRejections (node:internal/process/task_queues:84:21)
    2021-09-23T19:01:07.217Z [4567/78763] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
    2021-09-23T19:01:07.218Z [4567/78763] - error: Error [ERR_SERVER_NOT_RUNNING]: Server is not running.
        at new NodeError (node:internal/errors:371:5)
        at Server.close (node:net:1613:12)
        at Object.onceWrapper (node:events:509:28)
        at Server.emit (node:events:402:35)
        at emitCloseNT (node:net:1666:8)
        at processTicksAndRejections (node:internal/process/task_queues:82:21)
    3 restarts in 10 seconds, most likely an error on startup. Halting.

  • Starting with "daemon": false works, but I'd rather use the daemon

  • NodeBB Admin

    What version of node & npm are you using now?

  • @baris Versions below
    Node.js v16.10.0.
    npm --version 6.14.15

  • NodeBB Admin

    Can you try latest node 14.x, we don't official support 16 yet.

  • @baris ok. How can I downgrade ?

  • NodeBB Admin

  • @baris thanks. I removed NodeJS and reinstalled it using 14.x version. NodeBB now looks like it starts using the daemon (according to the logs, although if I try nodebb stop it tells me NodeBB is already stopped), and I get 502 bad gateway - but nothing has changed in terms of overall directory structure and nginx config.

    So it looks like whilst the original odd message has cleared, it's not starting

    My other NodeBB site works fine

  • @phenomlab could you try deleting your log file and starting with ./nodebb slog again?

  • @pitaj doesn't seem to do anything other than this

    Starting NodeBB with logging output
    Hit Ctrl-C to exit
    The NodeBB process will continue to run in the background
    Use "./nodebb stop" to stop the NodeBB server
    tail: cannot open './logs/output.log' for reading: No such file or directory
    tail: './logs/output.log' has appeared;  following new file

  • At this point, I'm totally stumped. The only other option I have available is to create a new instance and attach the current database to that to see if this resolves the issue or not.

    Failing that, I'm at a total loss here.

  • @PitaJ @baris I've been looking into this more, and but when I start NodeBB I get this message

    2021-09-26T19:52:22.547Z [4567/349055] - info: Enabling 'trust proxy'
    2021-09-26T19:52:22.550Z [4567/349055] - error: NodeBB address in use, exiting...
    Error: listen EADDRINUSE: address already in use
        at Server.setupListenHandle [as _listen2] (net.js:1320:16)
        at listenInCluster (net.js:1368:12)
        at doListen (net.js:1505:7)
        at processTicksAndRejections (internal/process/task_queues.js:83:21)
    2021-09-26T19:52:22.552Z [4567/349055] - error: uncaughtException: listen EADDRINUSE: address already in use
    Error: listen EADDRINUSE: address already in use
    3 restarts in 10 seconds, most likely an error on startup. Halting.

    The problem is, the port isn't actively being used anywhere. I have another NodeBB instance running on 4568, but that's it.

    Any thoughts ?


  • @phenomlab I don't know what to tell you. It's not lying about the address being in use.

    Does it work if you run node app? If not, it's definitely a rogue process left running on that port.

Suggested Topics

  • 1
  • 4
  • 3
  • 13
  • 6
| | | |