Solved Error After Install

[jamslatt]

I followed the install directions on the docs but was never given the NodeBB Setup Completed. message or prompted to enter an admin u and p so IDK if that is what went wrong but now when I ./nodebb start I get this:

Error: Failed to lookup view "500" in views directory "/opt/nodebb/build/public/templates"
    at EventEmitter.render (/opt/nodebb/node_modules/express/lib/application.js:580:17)
    at ServerResponse.render (/opt/nodebb/node_modules/express/lib/response.js:971:7)
    at content (/opt/nodebb/src/middleware/render.js:70:15)
    at /opt/nodebb/node_modules/async/dist/async.js:3830:24
    at replenish (/opt/nodebb/node_modules/async/dist/async.js:946:17)
    at /opt/nodebb/node_modules/async/dist/async.js:950:9
    at eachOfLimit (/opt/nodebb/node_modules/async/dist/async.js:975:24)
    at /opt/nodebb/node_modules/async/dist/async.js:980:16
    at eachOf (/opt/nodebb/node_modules/async/dist/async.js:1051:5)
    at _parallel (/opt/nodebb/node_modules/async/dist/async.js:3829:5)
    at Object.parallelLimit [as parallel] (/opt/nodebb/node_modules/async/dist/async.js:3912:5)
    at async.waterfall.str (/opt/nodebb/src/middleware/render.js:65:12)
    at nextTask (/opt/nodebb/node_modules/async/dist/async.js:5273:14)
    at next (/opt/nodebb/node_modules/async/dist/async.js:5280:9)
    at /opt/nodebb/node_modules/async/dist/async.js:906:16
    at fireFilterHook (/opt/nodebb/src/plugins/hooks.js:110:11)

Any ideas?

Info:

Digital Ocean Ubuntu 16.04
Installed as root
Located in ~/opt/nodebb

[PitaJ]

Do you have a preexisting database? Have you tried running ./nodebb setup again? Have you tried running npm install again? Have you tried running ./nodebb build?

[jamslatt]

Looks like my mongodb is failing:

[email protected]:/opt/nodebb# service mongod status
● mongod.service
   Loaded: not-found (Reason: No such file or directory)
   Active: failed (Result: exit-code) since Sun 2017-07-02 05:28:18 UTC; 24h ago
 Main PID: 20144 (code=exited, status=100)

Jul 02 05:28:18 nodebb systemd[1]: mongod.service: Main process exited, code=exited, status=100/n/a
Jul 02 05:28:18 nodebb systemd[1]: mongod.service: Unit entered failed state.
Jul 02 05:28:18 nodebb systemd[1]: mongod.service: Failed with result 'exit-code'.
Jul 02 05:28:28 nodebb systemd[1]: Stopped High-performance, schema-free document-oriented database.
[email protected]:/opt/nodebb#

[PitaJ]

What OS and what version of said OS?

[jamslatt]

Well I just tried to do a fresh install and now when I run the npm i --production I get:

---

Killed           ..] / extract:nodebb-theme-persona: sill gunzTarPerm extractEntry test/less/errors/mixed-mixin-definition-args-2.txt
child_process.js:524
    throw err;
    ^

Error: Command failed: npm i --production
    at checkExecSyncError (child_process.js:481:13)
    at Object.execSync (child_process.js:521:13)
    at Object.<anonymous> (/home/james/nodebb/nodebb:17:9)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.runMain (module.js:604:10)
    at run (bootstrap_node.js:389:7)

(but mongodb is working)

[PitaJ]

You might try increasing the available memory or adding swap space.

[jamslatt]

Looks like it is working. You are a G dude. (FYI yall should put under your system requirements >512mb ram) if that is a common issue.

[jamslatt]

Well now the site is live but the default theme is all fucked. http://exo.slatt.in/

[PitaJ]

Try running ./nodebb build

[jamslatt]

@pitaj I did. Is it because I am using :80 instead of the default.

[PitaJ]

Hmmm. Well if you're running it with sudo then that could cause issues. Try running it with :4567 first.

[jamslatt]

Just did this:

---

[email protected]:/home/james/nodebb# ./nodebb build
[deprecated] `String.prototype.rtrim` is deprecated as of NodeBB v1.5; use `utils.rtrim` instead.
3/7 06:44:03 [1878] - info: [build] Building in parallel mode
3/7 06:44:03 [1878] - info: [build]         plugin static dirs  build started
3/7 06:44:03 [1878] - info: [build]          requirejs modules  build started
3/7 06:44:03 [1878] - info: [build]           client js bundle  build started
3/7 06:44:03 [1878] - info: [build]            admin js bundle  build started
3/7 06:44:03 [1878] - info: [build]         client side styles  build started
3/7 06:44:03 [1878] - info: [build] admin control panel styles  build started
3/7 06:44:03 [1878] - info: [build]                  templates  build started
3/7 06:44:03 [1878] - info: [build]                  languages  build started
3/7 06:44:03 [1878] - info: [build]                     sounds  build started
3/7 06:44:03 [1878] - info: [build]         plugin static dirs  build completed in 0.043sec
3/7 06:44:09 [1878] - info: [build]           client js bundle  build completed in 5.253sec
3/7 06:44:09 [1878] - info: [build]            admin js bundle  build completed in 5.249sec
3/7 06:44:09 [1878] - info: [build]                     sounds  build completed in 5.452sec
3/7 06:44:17 [1878] - info: [build] admin control panel styles  build completed in 13.331sec
3/7 06:44:19 [1878] - info: [build]          requirejs modules  build completed in 15.536sec
3/7 06:44:19 [1878] - info: [build]         client side styles  build completed in 15.53sec
3/7 06:44:19 [1878] - info: [build]                  templates  build completed in 15.974sec
3/7 06:44:20 [1878] - info: [build]                  languages  build completed in 16.966sec
3/7 06:44:20 [1878] - info: [build] Asset compilation successful. Completed in 17.007sec.
[email protected]:/home/james/nodebb# ./nodebb restart

New Port

http://exo.slatt.in:4567/

Still broken

[PitaJ]

@jamslatt looks like you just fixed it. What happened?

[jamslatt]

I re-ran the ./nodebb setup and IDK what happened but now I have it working. Thanks for the help!

[dm]

I had the same problem when I was playing with NodeBB on a $2.5 vps from Vultr (=512MB ram). htop shows me that build process uses all available ram and cpu. Deploying on a decent machine/vps would solve the problem, aternatively, I called build steps one at a time ( eg ./nodebb build languages , ./nodebb build 'client side styles' etc) . Hope this helps.