systemd service not working



  • I've followed the docs for installing NodeBB on one of our Ubuntu servers.

    I've installed Nodejs 6.10.2 - the LTS version - and Redis rather than MongoDB.

    Both are working, I can access Redis, read and write on it.

    I have two problems, but I'll focus here on systemd. I've created the service file, but it does not work. This is what I get when I check the status:

    nodebb.service - NodeBB forum for Node.js.
       Loaded: loaded (/lib/systemd/system/nodebb.service; enabled; vendor preset: enabled)
       Active: failed (Result: start-limit-hit) since Thu 2017-04-20 00:53:59 EDT; 1h 42min ago
         Docs: http://nodebb.readthedocs.io/en/latest/
      Process: 20405 ExecStart=/usr/bin/node /opt/nodebb/launcher.js --no-daemon --no-silent (code=exited, status=1/FAILURE)
     Main PID: 20405 (code=exited, status=1/FAILURE)
    
    Apr 20 00:53:59 .io systemd[1]: nodebb.service: Unit entered failed state.
    Apr 20 00:53:59 .io systemd[1]: nodebb.service: Failed with result 'exit-code'.
    Apr 20 00:53:59 .io systemd[1]: nodebb.service: Service hold-off time over, scheduling restart.
    Apr 20 00:53:59 .io systemd[1]: Stopped NodeBB forum for Node.js..
    Apr 20 00:53:59 .io systemd[1]: nodebb.service: Start request repeated too quickly.
    Apr 20 00:53:59 .io systemd[1]: Failed to start NodeBB forum for Node.js..
    Apr 20 00:53:59 .io systemd[1]: nodebb.service: Unit entered failed state.
    Apr 20 00:53:59 .io systemd[1]: nodebb.service: Failed with result 'start-limit-hit'.
    

  • Global Moderator

    @An_dz have you tried starting NodeBB with ./nodebb dev?



  • Disregard, I've found the problem. In one of my tries to fix the other bug I ended up writing launcher.js rather than loader.js. 😁 It's all fine now.


Log in to reply
 


Looks like your connection to NodeBB was lost, please wait while we try to reconnect.