systemd service not working

Technical Support
  • 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'.
    
  • @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.


Suggested Topics


  • 0 Votes
    15 Posts
    203 Views

    @tankerkiller125 Very strange. I'm using the latest version of highlight.js with my own functions I provided, and everything works as intended. I had an issue before where basic text was being detected as bash for example, meaning every word almost was a different colour!

    Now I've disabled the Markdown version and implemented my own, it looks so much better. I'm using a theme switcher I wrote so that when themes change, it also pulls the highlight.js theme css file.

  • Custom pages stopped working

    Unsolved Technical Support
    1
    0 Votes
    1 Posts
    120 Views

    I noticed that custom pages no longer work. I see the following records in the error logs. I uninstalled and reinstalled the nodebb-custom-pages plugin. I've done several reboots and builds but it didn't work. Why might the problem be caused?
    my NodeBB version: 2.2.5
    custom pages version: 1.3.3

    2022-07-25T11:06:33.959Z [4567/1887] - error: GET /iletisim Error: Failed to lookup view "iletisim" in views directory "/home/nodes/nodebb/build/public/templates" at Function.render (/home/nodes/nodebb/node_modules/express/lib/application.js:597:17) at ServerResponse.render (/home/nodes/nodebb/node_modules/express/lib/response.js:1039:7) at /home/nodes/nodebb/src/middleware/render.js:107:11 at new Promise (<anonymous>) at renderContent (/home/nodes/nodebb/src/middleware/render.js:106:10) at renderMethod (/home/nodes/nodebb/src/middleware/render.js:75:15) at async ServerResponse.renderOverride [as render] (/home/nodes/nodebb/src/middleware/render.js:96:5)
  • 0 Votes
    5 Posts
    370 Views

    @PitaJ Thanks...it worked

  • 0 Votes
    9 Posts
    3k Views

    There is a chrome extension "DarkReader" it converts any website to dark theme. Persona looks great when this extension is turned on.

  • 0 Votes
    6 Posts
    2k Views

    @pichalite

    I've removed the ADS and it's not working again ?