service: Start request repeated too quickly. (code=exited, status=127)
Clash Royale CLAN TAG#URR8PPP
0
I am simply trying to start my node application as a service I am pointing to the server.js file and have that set as executable.
I would like to have this node app restarting on server reboot and be able to generally just use it as a service.
/etc/systemd/system/parsoid.service
[Unit]
Description=MediaWiki Parsoid Server
[Service]
ExecStart=/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js
Restart=always
User=nobody
# Note Debian/Ubuntu uses 'nogroup', RHEL/Fedora uses 'nobody'
Group=nogroup
Environment=PATH=/usr/bin:/usr/local/bin
Environment=NODE_ENV=production
WorkingDirectory=/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid
[Install]
WantedBy=multi-user.target
However when checking if the service is running it does not start. The node app starts without problems by doing node /var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js.
Errors
root@server:/etc/systemd/system# systemctl status parsoid.service
● parsoid.service - MediaWiki Parsoid Server
Loaded: loaded (/etc/systemd/system/parsoid.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Sat 2018-12-15 20:35:57 GMT; 1s ago
Process: 8565 ExecStart=/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js (code=exited, status=127)
Main PID: 8565 (code=exited, status=127)
Dec 15 20:35:56 server.live-servers.net systemd[1]: parsoid.service: Unit entered failed state.
Dec 15 20:35:56 server.live-servers.net systemd[1]: parsoid.service: Failed with result 'exit-code'.
Dec 15 20:35:57 server.live-servers.net systemd[1]: parsoid.service: Service hold-off time over, scheduling restart.
Dec 15 20:35:57 server.live-servers.net systemd[1]: Stopped MediaWiki Parsoid Server.
Dec 15 20:35:57 server.live-servers.net systemd[1]: parsoid.service: Start request repeated too quickly.
Dec 15 20:35:57 server.live-servers.net systemd[1]: Failed to start MediaWiki Parsoid Server.
[Edit]
Dec 15 20:57:33 server88-208-249-95.live-servers.net systemd[1]: [/etc/systemd/system/parsoid.service:5] Executable path is not absolute, ignoring: node /var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js
Dec 15 20:57:33 server.live-servers.net systemd[1]: parsoid.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
root@server:/etc/systemd/system# /var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js
Error while reading config file: Error: ENOENT: no such file or directory, open '/etc/systemd/system/config.yaml
systemd services node.js systemctl
edited Dec 16 at 0:49
Filipe Brandenburger
6,8852734
asked Dec 15 at 20:40
Jamie Hutber
1021213
|
show 6 more comments
0
I am simply trying to start my node application as a service I am pointing to the server.js file and have that set as executable.
I would like to have this node app restarting on server reboot and be able to generally just use it as a service.
/etc/systemd/system/parsoid.service
[Unit]
Description=MediaWiki Parsoid Server
[Service]
ExecStart=/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js
Restart=always
User=nobody
# Note Debian/Ubuntu uses 'nogroup', RHEL/Fedora uses 'nobody'
Group=nogroup
Environment=PATH=/usr/bin:/usr/local/bin
Environment=NODE_ENV=production
WorkingDirectory=/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid
[Install]
WantedBy=multi-user.target
However when checking if the service is running it does not start. The node app starts without problems by doing node /var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js.
Errors
root@server:/etc/systemd/system# systemctl status parsoid.service
● parsoid.service - MediaWiki Parsoid Server
Loaded: loaded (/etc/systemd/system/parsoid.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Sat 2018-12-15 20:35:57 GMT; 1s ago
Process: 8565 ExecStart=/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js (code=exited, status=127)
Main PID: 8565 (code=exited, status=127)
Dec 15 20:35:56 server.live-servers.net systemd[1]: parsoid.service: Unit entered failed state.
Dec 15 20:35:56 server.live-servers.net systemd[1]: parsoid.service: Failed with result 'exit-code'.
Dec 15 20:35:57 server.live-servers.net systemd[1]: parsoid.service: Service hold-off time over, scheduling restart.
Dec 15 20:35:57 server.live-servers.net systemd[1]: Stopped MediaWiki Parsoid Server.
Dec 15 20:35:57 server.live-servers.net systemd[1]: parsoid.service: Start request repeated too quickly.
Dec 15 20:35:57 server.live-servers.net systemd[1]: Failed to start MediaWiki Parsoid Server.
[Edit]
Dec 15 20:57:33 server88-208-249-95.live-servers.net systemd[1]: [/etc/systemd/system/parsoid.service:5] Executable path is not absolute, ignoring: node /var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js
Dec 15 20:57:33 server.live-servers.net systemd[1]: parsoid.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
root@server:/etc/systemd/system# /var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js
Error while reading config file: Error: ENOENT: no such file or directory, open '/etc/systemd/system/config.yaml
systemd services node.js systemctl
edited Dec 16 at 0:49
Filipe Brandenburger
6,8852734
asked Dec 15 at 20:40
Jamie Hutber
1021213
1
As far as I know, node files won't run by default/"natively". Try running/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.jsin your terminal. To fix this, runwhereis nodeand prepend the binary path to theExecStart=statement.
– rudib
Dec 15 at 20:45
Very good point, give me 5, I think I can use this :)(
– Jamie Hutber
Dec 15 at 20:51
I've updated the question with the latest, but it seems to me.node ..bin/server.jswill work in the terminal, however service requires an absolute path, which means I have no way of telling it where the base path should be, in regards to getting the config.yml is. I guess I couldlnit?
– Jamie Hutber
Dec 15 at 21:02
1
See my first comment. Runwhereis nodeand use the absolute path to the node binary.
– rudib
Dec 15 at 21:03
2
ExecStart=/usr/bin/node /path/to/your/file.jsshould work fine.ExecStart=node /path/to/your/file.jswon't work asnodeis not an absolute path.
– rudib
Dec 15 at 21:13
|
show 6 more comments
0
0
0
I am simply trying to start my node application as a service I am pointing to the server.js file and have that set as executable.
I would like to have this node app restarting on server reboot and be able to generally just use it as a service.
/etc/systemd/system/parsoid.service
[Unit]
Description=MediaWiki Parsoid Server
[Service]
ExecStart=/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js
Restart=always
User=nobody
# Note Debian/Ubuntu uses 'nogroup', RHEL/Fedora uses 'nobody'
Group=nogroup
Environment=PATH=/usr/bin:/usr/local/bin
Environment=NODE_ENV=production
WorkingDirectory=/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid
[Install]
WantedBy=multi-user.target
However when checking if the service is running it does not start. The node app starts without problems by doing node /var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js.
Errors
root@server:/etc/systemd/system# systemctl status parsoid.service
● parsoid.service - MediaWiki Parsoid Server
Loaded: loaded (/etc/systemd/system/parsoid.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Sat 2018-12-15 20:35:57 GMT; 1s ago
Process: 8565 ExecStart=/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js (code=exited, status=127)
Main PID: 8565 (code=exited, status=127)
Dec 15 20:35:56 server.live-servers.net systemd[1]: parsoid.service: Unit entered failed state.
Dec 15 20:35:56 server.live-servers.net systemd[1]: parsoid.service: Failed with result 'exit-code'.
Dec 15 20:35:57 server.live-servers.net systemd[1]: parsoid.service: Service hold-off time over, scheduling restart.
Dec 15 20:35:57 server.live-servers.net systemd[1]: Stopped MediaWiki Parsoid Server.
Dec 15 20:35:57 server.live-servers.net systemd[1]: parsoid.service: Start request repeated too quickly.
Dec 15 20:35:57 server.live-servers.net systemd[1]: Failed to start MediaWiki Parsoid Server.
[Edit]
Dec 15 20:57:33 server88-208-249-95.live-servers.net systemd[1]: [/etc/systemd/system/parsoid.service:5] Executable path is not absolute, ignoring: node /var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js
Dec 15 20:57:33 server.live-servers.net systemd[1]: parsoid.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
root@server:/etc/systemd/system# /var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js
Error while reading config file: Error: ENOENT: no such file or directory, open '/etc/systemd/system/config.yaml
systemd services node.js systemctl
edited Dec 16 at 0:49
Filipe Brandenburger
6,8852734
asked Dec 15 at 20:40
Jamie Hutber
1021213
I am simply trying to start my node application as a service I am pointing to the server.js file and have that set as executable.
I would like to have this node app restarting on server reboot and be able to generally just use it as a service.
/etc/systemd/system/parsoid.service
[Unit]
Description=MediaWiki Parsoid Server
[Service]
ExecStart=/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js
Restart=always
User=nobody
# Note Debian/Ubuntu uses 'nogroup', RHEL/Fedora uses 'nobody'
Group=nogroup
Environment=PATH=/usr/bin:/usr/local/bin
Environment=NODE_ENV=production
WorkingDirectory=/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid
[Install]
WantedBy=multi-user.target
However when checking if the service is running it does not start. The node app starts without problems by doing node /var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js.
Errors
root@server:/etc/systemd/system# systemctl status parsoid.service
● parsoid.service - MediaWiki Parsoid Server
Loaded: loaded (/etc/systemd/system/parsoid.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Sat 2018-12-15 20:35:57 GMT; 1s ago
Process: 8565 ExecStart=/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js (code=exited, status=127)
Main PID: 8565 (code=exited, status=127)
Dec 15 20:35:56 server.live-servers.net systemd[1]: parsoid.service: Unit entered failed state.
Dec 15 20:35:56 server.live-servers.net systemd[1]: parsoid.service: Failed with result 'exit-code'.
Dec 15 20:35:57 server.live-servers.net systemd[1]: parsoid.service: Service hold-off time over, scheduling restart.
Dec 15 20:35:57 server.live-servers.net systemd[1]: Stopped MediaWiki Parsoid Server.
Dec 15 20:35:57 server.live-servers.net systemd[1]: parsoid.service: Start request repeated too quickly.
Dec 15 20:35:57 server.live-servers.net systemd[1]: Failed to start MediaWiki Parsoid Server.
[Edit]
Dec 15 20:57:33 server88-208-249-95.live-servers.net systemd[1]: [/etc/systemd/system/parsoid.service:5] Executable path is not absolute, ignoring: node /var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js
Dec 15 20:57:33 server.live-servers.net systemd[1]: parsoid.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
root@server:/etc/systemd/system# /var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js
Error while reading config file: Error: ENOENT: no such file or directory, open '/etc/systemd/system/config.yaml
systemd services node.js systemctl
systemd services node.js systemctl
edited Dec 16 at 0:49
Filipe Brandenburger
6,8852734
asked Dec 15 at 20:40
Jamie Hutber
1021213
edited Dec 16 at 0:49
Filipe Brandenburger
6,8852734
asked Dec 15 at 20:40
Jamie Hutber
1021213
edited Dec 16 at 0:49
Filipe Brandenburger
6,8852734
edited Dec 16 at 0:49
Filipe Brandenburger
6,8852734
edited Dec 16 at 0:49
Filipe Brandenburger
6,8852734
6,8852734
asked Dec 15 at 20:40
Jamie Hutber
1021213
asked Dec 15 at 20:40
Jamie Hutber
1021213
asked Dec 15 at 20:40
Jamie Hutber
1021213
1021213
1
As far as I know, node files won't run by default/"natively". Try running/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.jsin your terminal. To fix this, runwhereis nodeand prepend the binary path to theExecStart=statement.
– rudib
Dec 15 at 20:45
Very good point, give me 5, I think I can use this :)(
– Jamie Hutber
Dec 15 at 20:51
I've updated the question with the latest, but it seems to me.node ..bin/server.jswill work in the terminal, however service requires an absolute path, which means I have no way of telling it where the base path should be, in regards to getting the config.yml is. I guess I couldlnit?
– Jamie Hutber
Dec 15 at 21:02
1
See my first comment. Runwhereis nodeand use the absolute path to the node binary.
– rudib
Dec 15 at 21:03
2
ExecStart=/usr/bin/node /path/to/your/file.jsshould work fine.ExecStart=node /path/to/your/file.jswon't work asnodeis not an absolute path.
– rudib
Dec 15 at 21:13
|
show 6 more comments
1
As far as I know, node files won't run by default/"natively". Try running/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.jsin your terminal. To fix this, runwhereis nodeand prepend the binary path to theExecStart=statement.
– rudib
Dec 15 at 20:45
Very good point, give me 5, I think I can use this :)(
– Jamie Hutber
Dec 15 at 20:51
I've updated the question with the latest, but it seems to me.node ..bin/server.jswill work in the terminal, however service requires an absolute path, which means I have no way of telling it where the base path should be, in regards to getting the config.yml is. I guess I couldlnit?
– Jamie Hutber
Dec 15 at 21:02
1
See my first comment. Runwhereis nodeand use the absolute path to the node binary.
– rudib
Dec 15 at 21:03
2
ExecStart=/usr/bin/node /path/to/your/file.jsshould work fine.ExecStart=node /path/to/your/file.jswon't work asnodeis not an absolute path.
– rudib
Dec 15 at 21:13
1
1
As far as I know, node files won't run by default/"natively". Try running
/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js in your terminal. To fix this, run whereis node and prepend the binary path to the ExecStart= statement.– rudib
Dec 15 at 20:45
As far as I know, node files won't run by default/"natively". Try running
/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.js in your terminal. To fix this, run whereis node and prepend the binary path to the ExecStart= statement.– rudib
Dec 15 at 20:45
Very good point, give me 5, I think I can use this :)(
– Jamie Hutber
Dec 15 at 20:51
Very good point, give me 5, I think I can use this :)(
– Jamie Hutber
Dec 15 at 20:51
I've updated the question with the latest, but it seems to me.
node ..bin/server.js will work in the terminal, however service requires an absolute path, which means I have no way of telling it where the base path should be, in regards to getting the config.yml is. I guess I could ln it?– Jamie Hutber
Dec 15 at 21:02
I've updated the question with the latest, but it seems to me.
node ..bin/server.js will work in the terminal, however service requires an absolute path, which means I have no way of telling it where the base path should be, in regards to getting the config.yml is. I guess I could ln it?– Jamie Hutber
Dec 15 at 21:02
1
1
See my first comment. Run
whereis node and use the absolute path to the node binary.– rudib
Dec 15 at 21:03
See my first comment. Run
whereis node and use the absolute path to the node binary.– rudib
Dec 15 at 21:03
2
2
ExecStart=/usr/bin/node /path/to/your/file.js should work fine. ExecStart=node /path/to/your/file.js won't work as node is not an absolute path.– rudib
Dec 15 at 21:13
ExecStart=/usr/bin/node /path/to/your/file.js should work fine. ExecStart=node /path/to/your/file.js won't work as node is not an absolute path.– rudib
Dec 15 at 21:13
|
show 6 more comments
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
);
);
draft saved
draft discarded
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%2funix.stackexchange.com%2fquestions%2f489207%2fservice-start-request-repeated-too-quickly-code-exited-status-127%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
draft saved
draft discarded
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%2funix.stackexchange.com%2fquestions%2f489207%2fservice-start-request-repeated-too-quickly-code-exited-status-127%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
1
As far as I know, node files won't run by default/"natively". Try running
/var/www/gwart/mediawiki/extensions/VisualEditor/parsoid/bin/server.jsin your terminal. To fix this, runwhereis nodeand prepend the binary path to theExecStart=statement.– rudib
Dec 15 at 20:45
Very good point, give me 5, I think I can use this :)(
– Jamie Hutber
Dec 15 at 20:51
I've updated the question with the latest, but it seems to me.
node ..bin/server.jswill work in the terminal, however service requires an absolute path, which means I have no way of telling it where the base path should be, in regards to getting the config.yml is. I guess I couldlnit?– Jamie Hutber
Dec 15 at 21:02
1
See my first comment. Run
whereis nodeand use the absolute path to the node binary.– rudib
Dec 15 at 21:03
2
ExecStart=/usr/bin/node /path/to/your/file.jsshould work fine.ExecStart=node /path/to/your/file.jswon't work asnodeis not an absolute path.– rudib
Dec 15 at 21:13