What do I do...?



  • 
    > nodebb@1.0.1-auto.0 start /root/nodebb
    > node loader.js
    
    sh: 1: node: not found
    
    npm ERR! Linux 3.19.8-031908-generic
    npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
    npm ERR! node v4.2.6
    npm ERR! npm  v3.5.2
    npm ERR! file sh
    npm ERR! code ELIFECYCLE
    npm ERR! errno ENOENT
    npm ERR! syscall spawn
    npm ERR! nodebb@1.0.1-auto.0 start: `node loader.js`
    npm ERR! spawn ENOENT
    npm ERR!
    npm ERR! Failed at the nodebb@1.0.1-auto.0 start script 'node loader.js'.
    npm ERR! Make sure you have the latest version of node.js and npm installed.
    npm ERR! If you do, this is most likely a problem with the nodebb package,
    npm ERR! not with npm itself.
    npm ERR! Tell the author that this fails on your system:
    npm ERR!     node loader.js
    npm ERR! You can get information on how to open an issue for this project with:
    npm ERR!     npm bugs nodebb
    npm ERR! Or if that isn't available, you can get their info via:
    npm ERR!     npm owner ls nodebb
    npm ERR! There is likely additional logging output above.
    
    npm ERR! Please include the following file with any support request:
    npm ERR!     /root/nodebb/npm-debug.log
    root@1661edb9fd10:~/nodebb# 0
    
    
    
     >0 info it worked if it ends with ok
    1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'start' ]
    2 info using npm@3.5.2
    3 info using node@v4.2.6
    4 verbose run-script [ 'prestart', 'start', 'poststart' ]
    5 info lifecycle nodebb@1.0.1-auto.0~prestart: nodebb@1.0.1-auto.0
    6 silly lifecycle nodebb@1.0.1-auto.0~prestart: no script for prestart, continuing
    7 info lifecycle nodebb@1.0.1-auto.0~start: nodebb@1.0.1-auto.0
    8 verbose lifecycle nodebb@1.0.1-auto.0~start: unsafe-perm in lifecycle true
    9 verbose lifecycle nodebb@1.0.1-auto.0~start: PATH: /usr/share/npm/bin/node-gyp-bin:/root/nodebb/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
    10 verbose lifecycle nodebb@1.0.1-auto.0~start: CWD: /root/nodebb
    11 silly lifecycle nodebb@1.0.1-auto.0~start: Args: [ '-c', 'node loader.js' ]
    12 info lifecycle nodebb@1.0.1-auto.0~start: Failed to exec start script
    13 verbose stack Error: nodebb@1.0.1-auto.0 start: `node loader.js`
    13 verbose stack spawn ENOENT
    13 verbose stack     at ChildProcess.<anonymous> (/usr/share/npm/lib/utils/spawn.js:17:16)
    13 verbose stack     at emitTwo (events.js:87:13)
    13 verbose stack     at ChildProcess.emit (events.js:172:7)
    13 verbose stack     at maybeClose (internal/child_process.js:821:16)
    13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
    14 verbose pkgid nodebb@1.0.1-auto.0
    15 verbose cwd /root/nodebb
    16 error Linux 3.19.8-031908-generic
    17 error argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
    18 error node v4.2.6
    19 error npm  v3.5.2
    20 error file sh
    21 error code ELIFECYCLE
    22 error errno ENOENT
    23 error syscall spawn
    24 error nodebb@1.0.1-auto.0 start: `node loader.js`
    24 error spawn ENOENT
    25 error Failed at the nodebb@1.0.1-auto.0 start script 'node loader.js'.
    25 error Make sure you have the latest version of node.js and npm installed.
    25 error If you do, this is most likely a problem with the nodebb package,
    25 error not with npm itself.
    25 error Tell the author that this fails on your system:
    25 error     node loader.js
    25 error You can get information on how to open an issue for this project with:
    25 error     npm bugs nodebb
    25 error Or if that isn't available, you can get their info via:
    25 error     npm owner ls nodebb
    25 error There is likely additional logging output above.
    26 verbose exit [ 1, true ]


  • Do you have command 'node' beyond 'nodejs'?
    Those error massages seem to say it.

    If you don't, there will be may ways to solve it depend on what kind of your system, BUT simply just make a sym link.

    which node 
    cd /usr/bin/
    ln -s nodejs node
    

Log in to reply
 


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