Mixing
Systemd + NPM start
I can't seem to be able to start my express server through Systemd (ExecStart=/usr/bin/npm run start). It does work when I run the command manually. Here is the stack trace:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli '/usr/bin/npm',
1 verbose cli 'run',
1 verbose cli 'start',
1 verbose cli '--prefix',
1 verbose cli '/opt/par/p-web' ]
2 info using npm@6.4.1
3 info using node@v10.13.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle p-web@1.0.0~prestart: p-web@1.0.0
6 info lifecycle p-web@1.0.0~start: p-web@1.0.0
7 verbose lifecycle p-web@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle p-web@1.0.0~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/opt/par/p-web/node_modules/.bin:/usr/bin:/usr/local/bin
9 verbose lifecycle p-web@1.0.0~start: CWD: /opt/par/p-web
10 silly lifecycle p-web@1.0.0~start: Args: [ '-c', 'node server/server.js' ]
11 info lifecycle p-web@1.0.0~start: Failed to exec start script
12 silly lifecycle p-web@1.0.0~start: Returned: code: -2 signal: null
13 info lifecycle p-web@1.0.0~start: Failed to exec start script
14 verbose stack Error: p-web@1.0.0 start: `node server/server.js`
14 verbose stack spawn sh ENOENT
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19)
14 verbose stack at onErrorNT (internal/child_process.js:407:16)
14 verbose stack at process._tickCallback (internal/process/next_tick.js:63:19)
15 verbose pkgid p-web@1.0.0
16 verbose cwd /opt/par/p-web
17 verbose Linux 4.4.0-1072-aws
18 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "start" "--prefix" "/opt/par/p-web"
19 verbose node v10.13.0
20 verbose npm v6.4.1
21 error file sh
22 error path sh
23 error code ELIFECYCLE
24 error errno ENOENT
25 error syscall spawn sh
26 error p-web@1.0.0 start: `node server/server.js`
26 error spawn sh ENOENT
27 error Failed at the p-web@1.0.0 start script.
27 error This is probably not a problem with npm. There is likely additional logging output above.
28 verbose exit [ 1, true ]
Any ideas?
node.js npm systemd
asked Nov 22 '18 at 12:32
KoreKore
1431112
add a comment |
I can't seem to be able to start my express server through Systemd (ExecStart=/usr/bin/npm run start). It does work when I run the command manually. Here is the stack trace:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli '/usr/bin/npm',
1 verbose cli 'run',
1 verbose cli 'start',
1 verbose cli '--prefix',
1 verbose cli '/opt/par/p-web' ]
2 info using npm@6.4.1
3 info using node@v10.13.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle p-web@1.0.0~prestart: p-web@1.0.0
6 info lifecycle p-web@1.0.0~start: p-web@1.0.0
7 verbose lifecycle p-web@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle p-web@1.0.0~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/opt/par/p-web/node_modules/.bin:/usr/bin:/usr/local/bin
9 verbose lifecycle p-web@1.0.0~start: CWD: /opt/par/p-web
10 silly lifecycle p-web@1.0.0~start: Args: [ '-c', 'node server/server.js' ]
11 info lifecycle p-web@1.0.0~start: Failed to exec start script
12 silly lifecycle p-web@1.0.0~start: Returned: code: -2 signal: null
13 info lifecycle p-web@1.0.0~start: Failed to exec start script
14 verbose stack Error: p-web@1.0.0 start: `node server/server.js`
14 verbose stack spawn sh ENOENT
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19)
14 verbose stack at onErrorNT (internal/child_process.js:407:16)
14 verbose stack at process._tickCallback (internal/process/next_tick.js:63:19)
15 verbose pkgid p-web@1.0.0
16 verbose cwd /opt/par/p-web
17 verbose Linux 4.4.0-1072-aws
18 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "start" "--prefix" "/opt/par/p-web"
19 verbose node v10.13.0
20 verbose npm v6.4.1
21 error file sh
22 error path sh
23 error code ELIFECYCLE
24 error errno ENOENT
25 error syscall spawn sh
26 error p-web@1.0.0 start: `node server/server.js`
26 error spawn sh ENOENT
27 error Failed at the p-web@1.0.0 start script.
27 error This is probably not a problem with npm. There is likely additional logging output above.
28 verbose exit [ 1, true ]
Any ideas?
node.js npm systemd
asked Nov 22 '18 at 12:32
KoreKore
1431112
it seems your system doesn't recognizenodeunder your system $PATH. Or the actual path you want node to run
– enapupe
Nov 22 '18 at 12:38
I debugged this to the best of my ability, and it does not seem to be the case :(
– Kore
Nov 22 '18 at 12:48
Just run with absolute paths to both node and the server/server to see if it works, if it does you'll have isolated the issue.
– enapupe
Nov 22 '18 at 14:16
It doesnt run with absolute paths
– Kore
Nov 22 '18 at 14:57
what's the output? I think if you update your question with abs paths it could be easier to debug
– enapupe
Nov 22 '18 at 16:01
add a comment |
I can't seem to be able to start my express server through Systemd (ExecStart=/usr/bin/npm run start). It does work when I run the command manually. Here is the stack trace:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli '/usr/bin/npm',
1 verbose cli 'run',
1 verbose cli 'start',
1 verbose cli '--prefix',
1 verbose cli '/opt/par/p-web' ]
2 info using npm@6.4.1
3 info using node@v10.13.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle p-web@1.0.0~prestart: p-web@1.0.0
6 info lifecycle p-web@1.0.0~start: p-web@1.0.0
7 verbose lifecycle p-web@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle p-web@1.0.0~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/opt/par/p-web/node_modules/.bin:/usr/bin:/usr/local/bin
9 verbose lifecycle p-web@1.0.0~start: CWD: /opt/par/p-web
10 silly lifecycle p-web@1.0.0~start: Args: [ '-c', 'node server/server.js' ]
11 info lifecycle p-web@1.0.0~start: Failed to exec start script
12 silly lifecycle p-web@1.0.0~start: Returned: code: -2 signal: null
13 info lifecycle p-web@1.0.0~start: Failed to exec start script
14 verbose stack Error: p-web@1.0.0 start: `node server/server.js`
14 verbose stack spawn sh ENOENT
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19)
14 verbose stack at onErrorNT (internal/child_process.js:407:16)
14 verbose stack at process._tickCallback (internal/process/next_tick.js:63:19)
15 verbose pkgid p-web@1.0.0
16 verbose cwd /opt/par/p-web
17 verbose Linux 4.4.0-1072-aws
18 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "start" "--prefix" "/opt/par/p-web"
19 verbose node v10.13.0
20 verbose npm v6.4.1
21 error file sh
22 error path sh
23 error code ELIFECYCLE
24 error errno ENOENT
25 error syscall spawn sh
26 error p-web@1.0.0 start: `node server/server.js`
26 error spawn sh ENOENT
27 error Failed at the p-web@1.0.0 start script.
27 error This is probably not a problem with npm. There is likely additional logging output above.
28 verbose exit [ 1, true ]
Any ideas?
node.js npm systemd
asked Nov 22 '18 at 12:32
KoreKore
1431112
I can't seem to be able to start my express server through Systemd (ExecStart=/usr/bin/npm run start). It does work when I run the command manually. Here is the stack trace:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node',
1 verbose cli '/usr/bin/npm',
1 verbose cli 'run',
1 verbose cli 'start',
1 verbose cli '--prefix',
1 verbose cli '/opt/par/p-web' ]
2 info using npm@6.4.1
3 info using node@v10.13.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle p-web@1.0.0~prestart: p-web@1.0.0
6 info lifecycle p-web@1.0.0~start: p-web@1.0.0
7 verbose lifecycle p-web@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle p-web@1.0.0~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/opt/par/p-web/node_modules/.bin:/usr/bin:/usr/local/bin
9 verbose lifecycle p-web@1.0.0~start: CWD: /opt/par/p-web
10 silly lifecycle p-web@1.0.0~start: Args: [ '-c', 'node server/server.js' ]
11 info lifecycle p-web@1.0.0~start: Failed to exec start script
12 silly lifecycle p-web@1.0.0~start: Returned: code: -2 signal: null
13 info lifecycle p-web@1.0.0~start: Failed to exec start script
14 verbose stack Error: p-web@1.0.0 start: `node server/server.js`
14 verbose stack spawn sh ENOENT
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19)
14 verbose stack at onErrorNT (internal/child_process.js:407:16)
14 verbose stack at process._tickCallback (internal/process/next_tick.js:63:19)
15 verbose pkgid p-web@1.0.0
16 verbose cwd /opt/par/p-web
17 verbose Linux 4.4.0-1072-aws
18 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "start" "--prefix" "/opt/par/p-web"
19 verbose node v10.13.0
20 verbose npm v6.4.1
21 error file sh
22 error path sh
23 error code ELIFECYCLE
24 error errno ENOENT
25 error syscall spawn sh
26 error p-web@1.0.0 start: `node server/server.js`
26 error spawn sh ENOENT
27 error Failed at the p-web@1.0.0 start script.
27 error This is probably not a problem with npm. There is likely additional logging output above.
28 verbose exit [ 1, true ]
Any ideas?
node.js npm systemd
node.js npm systemd
asked Nov 22 '18 at 12:32
KoreKore
1431112
asked Nov 22 '18 at 12:32
KoreKore
1431112
edited Nov 22 '18 at 13:05
Kore
asked Nov 22 '18 at 12:32
KoreKore
1431112
asked Nov 22 '18 at 12:32
KoreKore
1431112
asked Nov 22 '18 at 12:32
KoreKore
1431112
1431112
it seems your system doesn't recognizenodeunder your system $PATH. Or the actual path you want node to run
– enapupe
Nov 22 '18 at 12:38
I debugged this to the best of my ability, and it does not seem to be the case :(
– Kore
Nov 22 '18 at 12:48
Just run with absolute paths to both node and the server/server to see if it works, if it does you'll have isolated the issue.
– enapupe
Nov 22 '18 at 14:16
It doesnt run with absolute paths
– Kore
Nov 22 '18 at 14:57
what's the output? I think if you update your question with abs paths it could be easier to debug
– enapupe
Nov 22 '18 at 16:01
add a comment |
it seems your system doesn't recognizenodeunder your system $PATH. Or the actual path you want node to run
– enapupe
Nov 22 '18 at 12:38
I debugged this to the best of my ability, and it does not seem to be the case :(
– Kore
Nov 22 '18 at 12:48
Just run with absolute paths to both node and the server/server to see if it works, if it does you'll have isolated the issue.
– enapupe
Nov 22 '18 at 14:16
It doesnt run with absolute paths
– Kore
Nov 22 '18 at 14:57
what's the output? I think if you update your question with abs paths it could be easier to debug
– enapupe
Nov 22 '18 at 16:01
it seems your system doesn't recognize
node under your system $PATH. Or the actual path you want node to run– enapupe
Nov 22 '18 at 12:38
it seems your system doesn't recognize
node under your system $PATH. Or the actual path you want node to run– enapupe
Nov 22 '18 at 12:38
I debugged this to the best of my ability, and it does not seem to be the case :(
– Kore
Nov 22 '18 at 12:48
I debugged this to the best of my ability, and it does not seem to be the case :(
– Kore
Nov 22 '18 at 12:48
Just run with absolute paths to both node and the server/server to see if it works, if it does you'll have isolated the issue.
– enapupe
Nov 22 '18 at 14:16
Just run with absolute paths to both node and the server/server to see if it works, if it does you'll have isolated the issue.
– enapupe
Nov 22 '18 at 14:16
It doesnt run with absolute paths
– Kore
Nov 22 '18 at 14:57
It doesnt run with absolute paths
– Kore
Nov 22 '18 at 14:57
what's the output? I think if you update your question with abs paths it could be easier to debug
– enapupe
Nov 22 '18 at 16:01
what's the output? I think if you update your question with abs paths it could be easier to debug
– enapupe
Nov 22 '18 at 16:01
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53431121%2fsystemd-npm-start%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53431121%2fsystemd-npm-start%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
it seems your system doesn't recognize
nodeunder your system $PATH. Or the actual path you want node to run– enapupe
Nov 22 '18 at 12:38
I debugged this to the best of my ability, and it does not seem to be the case :(
– Kore
Nov 22 '18 at 12:48
Just run with absolute paths to both node and the server/server to see if it works, if it does you'll have isolated the issue.
– enapupe
Nov 22 '18 at 14:16
It doesnt run with absolute paths
– Kore
Nov 22 '18 at 14:57
what's the output? I think if you update your question with abs paths it could be easier to debug
– enapupe
Nov 22 '18 at 16:01