Well I have manages to break draws-manager. I get the following messages when I check the status: ● draws-manager.service - DRAWS™ Manager - A web application to manage the DRAW™ HAT configuration. Loaded: loaded (/etc/systemd/system/draws-manager.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2020-04-05 12:15:39 CDT; 2min 26s ago Docs: https://github.com/nwdigitalradio/draws-manager Process: 456 ExecStart=/usr/bin/npm start (code=exited, status=1/FAILURE) Main PID: 456 (code=exited, status=1/FAILURE) Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! errno 1 Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! webapp@0.0.1 start: `node ./bin/www` Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! Exit status 1 Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! Failed at the webapp@0.0.1 start script. Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above. Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! A complete log of this run can be found in: Apr 05 12:15:39 DRAWS15 npm[456]: npm ERR! /root/.npm/_logs/2020-04-05T17_15_39_643Z-debug.log Apr 05 12:15:39 DRAWS15 systemd[1]: draws-manager.service: Main process exited, code=exited, status=1/FAILURE Apr 05 12:15:39 DRAWS15 systemd[1]: draws-manager.service: Failed with result 'exit-code'. additional log info: 0 info it worked if it ends with ok 1 warn npm npm does not support Node.js v10.15.2 2 warn npm You should probably upgrade to a newer version of node as we 3 warn npm can't make any promises that npm will work with this version. 4 warn npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9. 5 warn npm You can find the latest version at https://nodejs.org/ 6 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ] 7 info using npm@5.8.0 8 info using node@... 9 verbose run-script [ 'prestart', 'start', 'poststart' ] 10 info lifecycle webapp@0.0.1~prestart: webapp@0.0.1 11 info lifecycle webapp@0.0.1~start: webapp@0.0.1 12 verbose lifecycle webapp@0.0.1~start: unsafe-perm in lifecycle true 13 verbose lifecycle webapp@0.0.1~start: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/usr/local/var/draws-manager/webapp/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 14 verbose lifecycle webapp@0.0.1~start: CWD: /usr/local/var/draws-manager/webapp 15 silly lifecycle webapp@0.0.1~start: Args: [ '-c', 'node ./bin/www' ] 16 silly lifecycle webapp@0.0.1~start: Returned: code: 1 signal: null 17 info lifecycle webapp@0.0.1~start: Failed to exec start script 18 verbose stack Error: webapp@0.0.1 start: `node ./bin/www` 18 verbose stack Exit status 1 18 verbose stack at EventEmitter.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/index.js:283:16) 18 verbose stack at EventEmitter.emit (events.js:189:13) 18 verbose stack at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 18 verbose stack at ChildProcess.emit (events.js:189:13) 18 verbose stack at maybeClose (internal/child_process.js:970:16) 18 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5) 19 verbose pkgid webapp@0.0.1 20 verbose cwd /usr/local/var/draws-manager/webapp 21 verbose Linux 4.19.97-v7+ 22 verbose argv "/usr/bin/node" "/usr/bin/npm" "start" 23 verbose node v10.15.2 24 verbose npm v5.8.0 25 error code ELIFECYCLE 26 error errno 1 27 error webapp@0.0.1 start: `node ./bin/www` 27 error Exit status 1 28 error Failed at the webapp@0.0.1 start script. 28 error This is probably not a problem with npm. There is likely additional logging output above. 29 verbose exit [ 1, true ] Any ideas on how to fix this ? -Kb5zur David
On Sat, Apr 4, 2020 at 1:22 PM John D Hays - K7VE <john@...> wrote:
|
|