Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 0 info it worked if it ends with ok
- 1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
- 2 info using [email protected]
- 3 info using [email protected]
- 4 verbose run-script [ 'prestart', 'start', 'poststart' ]
- 5 info lifecycle [email protected]~prestart: [email protected]
- 6 info lifecycle [email protected]~start: [email protected]
- 7 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
- 8 verbose lifecycle [email protected]~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/misskey/misskey/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
- 9 verbose lifecycle [email protected]~start: CWD: /home/misskey/misskey
- 10 silly lifecycle [email protected]~start: Args: [ '-c', 'node ./built' ]
- 11 silly lifecycle [email protected]~start: Returned: code: 1 signal: null
- 12 info lifecycle [email protected]~start: Failed to exec start script
- 13 verbose stack Error: [email protected] start: `node ./built`
- 13 verbose stack Exit status 1
- 13 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
- 13 verbose stack at EventEmitter.emit (events.js:188:13)
- 13 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
- 13 verbose stack at ChildProcess.emit (events.js:188:13)
- 13 verbose stack at maybeClose (internal/child_process.js:978:16)
- 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)
- 14 verbose pkgid [email protected]
- 15 verbose cwd /home/misskey/misskey
- 16 verbose Linux 4.15.0-33-generic
- 17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
- 18 verbose node v11.7.0
- 19 verbose npm v6.5.0
- 20 error code ELIFECYCLE
- 21 error errno 1
- 22 error [email protected] start: `node ./built`
- 22 error Exit status 1
- 23 error Failed at the [email protected] start script.
- 23 error This is probably not a problem with npm. There is likely additional logging output above.
- 24 verbose exit [ 1, true ]
Advertisement
Add Comment
Please, Sign In to add comment
