|
From: Sidi L. <sid...@gm...> - 2018-06-24 07:57:06
|
Hi Torsten I did what you said, and it gave me the same error. Also, I've tried three different versions of nodejs, the results were same. This is the log 0 info it worked if it ends with ok 1 verbose cli [ '/home/public/nodejs/node/bin/node', 1 verbose cli '/home/public/nodejs/node/bin/npm', 1 verbose cli 'start' ] 2 info using npm@6.1.0 3 info using node@v10.4.1 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle mpmap.js@1.0.0~prestart: mpmap.js@1.0.0 6 info lifecycle mpmap.js@1.0.0~start: mpmap.js@1.0.0 7 verbose lifecycle mpmap.js@1.0.0~start: unsafe-perm in lifecycle true 8 verbose lifecycle mpmap.js@1.0.0~start: PATH: /home/public/nodejs/node/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/flightgear-mpmap.js/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/home/public/nodejs/node/bin 9 verbose lifecycle mpmap.js@1.0.0~start: CWD: /flightgear-mpmap.js 10 silly lifecycle mpmap.js@1.0.0~start: Args: [ '-c', 'node server.js' ] 11 silly lifecycle mpmap.js@1.0.0~start: Returned: code: 1 signal: null 12 info lifecycle mpmap.js@1.0.0~start: Failed to exec start script 13 verbose stack Error: mpmap.js@1.0.0 start: `node server.js` 13 verbose stack Exit status 1 13 verbose stack at EventEmitter.<anonymous> (/home/public/nodejs/node/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:304:16) 13 verbose stack at EventEmitter.emit (events.js:182:13) 13 verbose stack at ChildProcess.<anonymous> (/home/public/nodejs/node/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 13 verbose stack at ChildProcess.emit (events.js:182:13) 13 verbose stack at maybeClose (internal/child_process.js:961:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:5) 14 verbose pkgid mpmap.js@1.0.0 15 verbose cwd /flightgear-mpmap.js 16 verbose Linux 2.6.32-696.18.7.el6.x86_64 17 verbose argv "/home/public/nodejs/node/bin/node" "/home/public/nodejs/node/bin/npm" "start" 18 verbose node v10.4.1 19 verbose npm v6.1.0 20 error code ELIFECYCLE 21 error errno 1 22 error mpmap.js@1.0.0 start: `node server.js` 22 error Exit status 1 23 error Failed at the mpmap.js@1.0.0 start script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ] Best Regards, Sidi 2018-06-24 14:22 GMT+08:00 Torsten Dreyer <to...@t3...>: > >> npm ERR! code ELIFECYCLE >> >> npm ERR! errno 1 >> >> npm ERR! mpmap.js@1.0.0 start: `node server.js` >> >> npm ERR! Exit status 1 >> >> npm ERR! >> >> npm ERR! Failed at the mpmap.js@1.0.0 start script. >> >> npm ERR! This is probably not a problem with npm. There is likely >> additional logging output above. >> >> >> npm ERR! A complete log of this run can be found in: >> >> npm ERR! /root/.npm/_logs/2018-06-23T12_57_33_755Z-debug.log >> >> >> Do you know how to fix that? >> >> >> > Something has gone wrong with installation of your node modules. > Did you your "npm install" after "git pull" or after moving within the git > history? > Probably remove the node_modules directory and do "npm install" again. > Eventually have a lok in the debug.log as mentioned in the error message. > -- > > Torsten Dreyer > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > -- liang sidi |