NodeBB won't start anymore after installing theme.

Technical Support
  • Hello,

    My nodeBB software gets stuck on start.
    If I do ./nodebb start it says starting nodebb. but it looks like it can't get startet.

    I also did resetting the theme ./nodebb reset -t and I get the message theme is set to persona, but it still won't load.

    If I do ./nodebb log it says "3 restarts in 10 seconds, most likely an error on startup. Halting."

    Can somebody please help me with this?
    I made back-up from my data so my content is safe (this time 😛 )

  • @MJ try starting with ./nodebb dev and check for any errors in logs

  • NodeBB v1.1.2 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 1 process(es).
    
    28/9 13:51 [1653] - verbose: * using configuration stored in: /root/nodebb/config.json
    28/9 13:51 [1653] - info: Time: Wed Sep 28 2016 13:51:33 GMT-0400 (EDT)
    28/9 13:51 [1653] - info: Initializing NodeBB v1.1.2
    28/9 13:51 [1653] - verbose: * using mongo store at 127.0.0.1:27017
    28/9 13:51 [1653] - verbose: * using themes stored in: /root/nodebb/node_modules
    28/9 13:51 [1653] - warn: You have no mongo password setup!
    28/9 13:51 [1653] - info: [database] Checking database indices.
    28/9 13:51 [1653] - verbose: Checking dependencies for outdated modules
    28/9 13:51 [1653] - verbose: [notifications.init] Registering jobs.
    28/9 13:51 [1653] - error: SyntaxError: Unexpected string
        at Object.parse (native)
        at /root/nodebb/src/meta/themes.js:45:28
        at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:380:3)
    SyntaxError: Unexpected string
        at Object.parse (native)
        at /root/nodebb/src/meta/themes.js:45:28
        at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:380:3)
    28/9 13:51 [1653] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
    28/9 13:51 [1653] - info: [app] Database connection closed.
    28/9 13:51 [1653] - info: [app] Web server closed to connections.
    28/9 13:51 [1653] - info: [app] Shutdown complete.
    [cluster] Child Process (1653) has exited (code: 1, signal: null)
    [cluster] Spinning up another process...
    28/9 13:51 [1666] - verbose: * using configuration stored in: /root/nodebb/config.json
    28/9 13:51 [1666] - info: Time: Wed Sep 28 2016 13:51:37 GMT-0400 (EDT)
    28/9 13:51 [1666] - info: Initializing NodeBB v1.1.2
    28/9 13:51 [1666] - verbose: * using mongo store at 127.0.0.1:27017
    28/9 13:51 [1666] - verbose: * using themes stored in: /root/nodebb/node_modules
    28/9 13:51 [1666] - warn: You have no mongo password setup!
    28/9 13:51 [1666] - info: [database] Checking database indices.
    28/9 13:51 [1666] - verbose: Checking dependencies for outdated modules
    28/9 13:51 [1666] - verbose: [notifications.init] Registering jobs.
    28/9 13:51 [1666] - error: SyntaxError: Unexpected string
        at Object.parse (native)
        at /root/nodebb/src/meta/themes.js:45:28
        at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:380:3)
    SyntaxError: Unexpected string
        at Object.parse (native)
        at /root/nodebb/src/meta/themes.js:45:28
        at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:380:3)
    28/9 13:51 [1666] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
    28/9 13:51 [1666] - info: [app] Database connection closed.
    28/9 13:51 [1666] - info: [app] Web server closed to connections.
    28/9 13:51 [1666] - info: [app] Shutdown complete.
    [cluster] Child Process (1666) has exited (code: 1, signal: null)
    [cluster] Spinning up another process...
    28/9 13:51 [1679] - verbose: * using configuration stored in: /root/nodebb/config.json
    28/9 13:51 [1679] - info: Time: Wed Sep 28 2016 13:51:40 GMT-0400 (EDT)
    28/9 13:51 [1679] - info: Initializing NodeBB v1.1.2
    28/9 13:51 [1679] - verbose: * using mongo store at 127.0.0.1:27017
    28/9 13:51 [1679] - verbose: * using themes stored in: /root/nodebb/node_modules
    28/9 13:51 [1679] - warn: You have no mongo password setup!
    28/9 13:51 [1679] - info: [database] Checking database indices.
    28/9 13:51 [1679] - verbose: Checking dependencies for outdated modules
    28/9 13:51 [1679] - verbose: [notifications.init] Registering jobs.
    28/9 13:51 [1679] - error: SyntaxError: Unexpected string
        at Object.parse (native)
        at /root/nodebb/src/meta/themes.js:45:28
        at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:380:3)
    SyntaxError: Unexpected string
        at Object.parse (native)
        at /root/nodebb/src/meta/themes.js:45:28
        at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:380:3)
    28/9 13:51 [1679] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
    28/9 13:51 [1679] - info: [app] Database connection closed.
    28/9 13:51 [1679] - info: [app] Web server closed to connections.
    28/9 13:51 [1679] - info: [app] Shutdown complete.
    [cluster] Child Process (1679) has exited (code: 1, signal: null)
    [cluster] Spinning up another process...
    28/9 13:51 [1692] - verbose: * using configuration stored in: /root/nodebb/config.json
    28/9 13:51 [1692] - info: Time: Wed Sep 28 2016 13:51:43 GMT-0400 (EDT)
    28/9 13:51 [1692] - info: Initializing NodeBB v1.1.2
    28/9 13:51 [1692] - verbose: * using mongo store at 127.0.0.1:27017
    28/9 13:51 [1692] - verbose: * using themes stored in: /root/nodebb/node_modules
    28/9 13:51 [1692] - warn: You have no mongo password setup!
    28/9 13:51 [1692] - info: [database] Checking database indices.
    28/9 13:51 [1692] - verbose: Checking dependencies for outdated modules
    28/9 13:51 [1692] - verbose: [notifications.init] Registering jobs.
    28/9 13:51 [1692] - error: SyntaxError: Unexpected string
        at Object.parse (native)
        at /root/nodebb/src/meta/themes.js:45:28
        at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:380:3)
    SyntaxError: Unexpected string
        at Object.parse (native)
        at /root/nodebb/src/meta/themes.js:45:28
        at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:380:3)
    28/9 13:51 [1692] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
    28/9 13:51 [1692] - info: [app] Database connection closed.
    28/9 13:51 [1692] - info: [app] Web server closed to connections.
    28/9 13:51 [1692] - info: [app] Shutdown complete.
    3 restarts in 10 seconds, most likely an error on startup. Halting.
    
  • @MJ theme.json in one of your themes is invalid, I think. Try using http://jsonlint.com/ to check them.

  • @PitaJ i reset the theme with ./nodebb reset -t so it should be okay, or not?

    and if I need to test theme, can you explain please how I must do it sir?

  • @MJ do you have any themes besides persona installed? Try reinstalling persona, first, with npm remove nodebb-theme-persona and npm install nodebb-theme-persona. If that doesn't work, try deleting the node_modules directory and reinstalling everything with npm install.

    If that doesn't work, try copying the contents of node_modules/nodebb-plugin-persona/theme.json into that JSON validator I linked and making sure it's all valid.

  • wait I did test the files, and one did this.

    0_1475087829290_upload-a9a7a2df-33ba-42c7-9500-7dc49eb02a5e ,

  • @MJ yep. That's invalid JSON. It's missing a comma after the highlighted line.

  • @PitaJ can I uninstall that theme, and how?

  • @MJ probably just npm remove nodebb-theme-hexadecimal

  • @PitaJ I go try now

  • @PitaJ
    It worked sir 🙂

    Check PM please 🙂

  • Like @PitaJ said, the theme doesn't work because that line misses a comma. Put a comma after that description line and the theme should work, assuming nothing else is broken.

  • Hi all, today I just installed a cloud version and I can't change files myself. Faced with the same problem. I've changed the theme back to Persona and now can open no frontend nigher backend. It forwards me to the nodebb website and shows this message:

    Service Unavailable
    We couldn't reach the website you were looking to access. It may be offline temporarily, please try again later.

    How can I deal with it? Thanks


Suggested Topics


  • Using within the NodeBB mobile app

    Unsolved Technical Support
    1
    2 Votes
    1 Posts
    204 Views

    We want to use NodeBB in a part of our native application. Can we use basic forum functions like registration, new topic, post, groups, websocket, chat via API? Is there a document for this? Thanks.

  • 0 Votes
    2 Posts
    257 Views

    Try disabling the custom plugins and see if it helps.

  • Few questions about NodeBB

    Technical Support
    6
    0 Votes
    6 Posts
    672 Views

    @julian Clear enough, thank you so much.

  • 0 Votes
    1 Posts
    1k Views

    So... hello 🙂

    I was wondering if anyone has setup nodebb on Plesk Onyx succesfully?

    from what i can tell, everything is setup and working as it should, but I can not connect?...

    3/9 19:13 [7] - info: NodeBB v1.1.2 Copyright (C) 2013-2016 NodeBB Inc. 3/9 19:13 [7] - info: This program comes with ABSOLUTELY NO WARRANTY. 3/9 19:13 [7] - info: This is free software, and you are welcome to redistribute it under certain conditions. 3/9 19:13 [7] - info: 3/9 19:13 [7] - info: NodeBB Setup Triggered via Command Line Welcome to NodeBB! This looks like a new installation, so you'll have to answer a few questions about your environment before we can proceed. Press enter to accept the default setting (shown in brackets). URL used to access this NodeBB (http://localhost:4567) > [email protected] start /usr/src/app > node loader.js 3/9 19:14 [36] - info: Launching web installer on port 4567 3/9 19:14 [36] - info: Web installer listening on http://0.0.0.0:4567 npm info it worked if it ends with ok npm info using [email protected] npm info using [email protected] npm info prestart [email protected] npm info start [email protected]

    anyone have any experiance?

  • 0 Votes
    4 Posts
    1k Views

    @prog At current, no. Our servers are based in a New York datacenter, but we do not use CDN for global delivery of assets like the client js and css.