Forum not starting

Technical Support
  • NodeJS: v11.6.0
    NodeBB: latest (master branch)

    After updating the forum and nodejs it stopped working, logs lower.


    [cluster] Child Process (2717) has exited (code: null, signal: SIGTERM)
    NodeBB v1.11.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:
    Clustering enabled: Spinning up 3 process(es).
    2019-01-03T22:02:54.722Z [8000/689] - info: Initializing NodeBB v1.11.1
    2019-01-03T22:03:01.367Z [8001/690] - info: [] Restricting access to origin:*
    2019-01-03T22:03:01.374Z [8002/692] - info: [] Restricting access to origin:*
    2019-01-03T22:03:01.375Z [8000/689] - info: [] Restricting access to origin:*
    2019-01-03T22:03:03.115Z [8001/690] - info: [plugins/spam-be-gone] Settings loaded
    2019-01-03T22:03:03.118Z [8000/689] - info: [plugins/spam-be-gone] Settings loaded
    2019-01-03T22:03:03.153Z [8002/692] - info: [plugins/spam-be-gone] Settings loaded
    2019-01-03T22:03:03.245Z [8001/690] - info: Routes added
    2019-01-03T22:03:03.246Z [8000/689] - info: Routes added
    2019-01-03T22:03:03.252Z [8000/689] - info: NodeBB Ready
    2019-01-03T22:03:03.259Z [8001/690] - info: NodeBB Ready
    2019-01-03T22:03:03.262Z [8000/689] - info: Enabling 'trust proxy'
    2019-01-03T22:03:03.267Z [8000/689] - info: NodeBB is now listening on:
    2019-01-03T22:03:03.269Z [8001/690] - info: Enabling 'trust proxy'
    2019-01-03T22:03:03.275Z [8002/692] - info: Routes added
    2019-01-03T22:03:03.278Z [8001/690] - info: NodeBB is now listening on:
    2019-01-03T22:03:03.285Z [8002/692] - info: NodeBB Ready
    2019-01-03T22:03:03.289Z [8002/692] - info: Enabling 'trust proxy'
    2019-01-03T22:03:03.292Z [8002/692] - info: NodeBB is now listening on:
  • Try downgrading to Node 10, please

  • Fixed, the problem was on the nginx side;

Suggested Topics

  • Forum down after restart

    Solved Technical Support
    0 Votes
    76 Posts

    @PitaJ Sorry I'm a little late responding here. I've used systemd as defined below, which works fine, and survives a rebuilt and restart

    [Unit] Description=Sudonix Documentation= After=system.slice mongod.service [Service] Type=forking User=sudonix StandardOutput=syslog StandardError=syslog SyslogIdentifier=nodebb WorkingDirectory=/home/sudonix/nodebb PIDFile=/home/sudonix/nodebb/pidfile ExecStart=/usr/bin/env node loader.js Restart=always [Install]

    Many thanks for all the help and support. Greatly appreciated.

  • 0 Votes
    2 Posts
    324 Views This is a plugin that does it for topics.

    There is no built in way to do it in core. So to do it for categories you would have to fork and extend the above plugin.

  • 0 Votes
    46 Posts

    Thank you everybody for helping me with forum troubleshooting. The problem has been found. It's memory limit. After a few years of use, 512MB RAM + 256MB swap is not enough anymore (I have some suspicions that swap does not kick in, but it's a topic for a different story).

    If somebody searches, and no changes plugins, core, or hardware, and you do not have plugins that depend on external services - check if it's a memory issue.

  • 0 Votes
    2 Posts

    What logs are you looking at? Try loading a page while watching ./nodebb log. Also, try running ./nodebb build and restarting.

  • Nodebb not start

    Technical Support
    0 Votes
    3 Posts

    Seems like your Redis server is not running, did you install it onto your system?