system cron not running intended process scheduled for execution
up vote
0
down vote
favorite
I have node server that I want to restart whenever it stopped. For this case I setup system cron on ubuntu server to execute a simple bash script that will track node server every minute and log the server status. Now this cron trigger this bash script and logs relevant status every minute but node server doesn't execute(Using simple linux command I can check if node server running or not). When manually running that bash script node server starts but something happening when cron executes that script. I am trying to fix this meanwhile any help will be appreciated.
Thanks
linux bash shell ubuntu cron
asked Nov 10 at 12:06
Jai Narayan Singh
214
add a comment |
up vote
0
down vote
favorite
I have node server that I want to restart whenever it stopped. For this case I setup system cron on ubuntu server to execute a simple bash script that will track node server every minute and log the server status. Now this cron trigger this bash script and logs relevant status every minute but node server doesn't execute(Using simple linux command I can check if node server running or not). When manually running that bash script node server starts but something happening when cron executes that script. I am trying to fix this meanwhile any help will be appreciated.
Thanks
linux bash shell ubuntu cron
asked Nov 10 at 12:06
Jai Narayan Singh
214
Have you tried usingforeverfor auto-start of your node app? npmjs.com/package/forever
– ssemilla
Nov 10 at 13:24
Did you check the logs in/var/log/syslog?
– Samarth
Nov 10 at 14:49
After trying multiple options this solution works for me. Declaring PATH and SHELL in cron. I am using /bin/bash So explicitly adding these two solve this issue. @Samarth yes syslogs list script execution indeed.
– Jai Narayan Singh
2 days ago
@ssemilla Although I didn't tried this node tool but using forever in CLI mode good alternative.
– Jai Narayan Singh
2 days ago
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have node server that I want to restart whenever it stopped. For this case I setup system cron on ubuntu server to execute a simple bash script that will track node server every minute and log the server status. Now this cron trigger this bash script and logs relevant status every minute but node server doesn't execute(Using simple linux command I can check if node server running or not). When manually running that bash script node server starts but something happening when cron executes that script. I am trying to fix this meanwhile any help will be appreciated.
Thanks
linux bash shell ubuntu cron
asked Nov 10 at 12:06
Jai Narayan Singh
214
I have node server that I want to restart whenever it stopped. For this case I setup system cron on ubuntu server to execute a simple bash script that will track node server every minute and log the server status. Now this cron trigger this bash script and logs relevant status every minute but node server doesn't execute(Using simple linux command I can check if node server running or not). When manually running that bash script node server starts but something happening when cron executes that script. I am trying to fix this meanwhile any help will be appreciated.
Thanks
linux bash shell ubuntu cron
linux bash shell ubuntu cron
asked Nov 10 at 12:06
Jai Narayan Singh
214
asked Nov 10 at 12:06
Jai Narayan Singh
214
asked Nov 10 at 12:06
Jai Narayan Singh
214
asked Nov 10 at 12:06
Jai Narayan Singh
214
asked Nov 10 at 12:06
Jai Narayan Singh
214
214
Have you tried usingforeverfor auto-start of your node app? npmjs.com/package/forever
– ssemilla
Nov 10 at 13:24
Did you check the logs in/var/log/syslog?
– Samarth
Nov 10 at 14:49
After trying multiple options this solution works for me. Declaring PATH and SHELL in cron. I am using /bin/bash So explicitly adding these two solve this issue. @Samarth yes syslogs list script execution indeed.
– Jai Narayan Singh
2 days ago
@ssemilla Although I didn't tried this node tool but using forever in CLI mode good alternative.
– Jai Narayan Singh
2 days ago
add a comment |
Have you tried usingforeverfor auto-start of your node app? npmjs.com/package/forever
– ssemilla
Nov 10 at 13:24
Did you check the logs in/var/log/syslog?
– Samarth
Nov 10 at 14:49
After trying multiple options this solution works for me. Declaring PATH and SHELL in cron. I am using /bin/bash So explicitly adding these two solve this issue. @Samarth yes syslogs list script execution indeed.
– Jai Narayan Singh
2 days ago
@ssemilla Although I didn't tried this node tool but using forever in CLI mode good alternative.
– Jai Narayan Singh
2 days ago
Have you tried using
forever for auto-start of your node app? npmjs.com/package/forever– ssemilla
Nov 10 at 13:24
Have you tried using
forever for auto-start of your node app? npmjs.com/package/forever– ssemilla
Nov 10 at 13:24
Did you check the logs in
/var/log/syslog?– Samarth
Nov 10 at 14:49
Did you check the logs in
/var/log/syslog?– Samarth
Nov 10 at 14:49
After trying multiple options this solution works for me. Declaring PATH and SHELL in cron. I am using /bin/bash So explicitly adding these two solve this issue. @Samarth yes syslogs list script execution indeed.
– Jai Narayan Singh
2 days ago
After trying multiple options this solution works for me. Declaring PATH and SHELL in cron. I am using /bin/bash So explicitly adding these two solve this issue. @Samarth yes syslogs list script execution indeed.
– Jai Narayan Singh
2 days ago
@ssemilla Although I didn't tried this node tool but using forever in CLI mode good alternative.
– Jai Narayan Singh
2 days ago
@ssemilla Although I didn't tried this node tool but using forever in CLI mode good alternative.
– Jai Narayan Singh
2 days ago
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
instead of doing this with cron i think you have to use spervisor in order to keep the process running check this supervisor website
answered 2 days ago
mohammad zein
8612
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
instead of doing this with cron i think you have to use spervisor in order to keep the process running check this supervisor website
answered 2 days ago
mohammad zein
8612
add a comment |
up vote
0
down vote
instead of doing this with cron i think you have to use spervisor in order to keep the process running check this supervisor website
answered 2 days ago
mohammad zein
8612
add a comment |
up vote
0
down vote
up vote
0
down vote
instead of doing this with cron i think you have to use spervisor in order to keep the process running check this supervisor website
answered 2 days ago
mohammad zein
8612
instead of doing this with cron i think you have to use spervisor in order to keep the process running check this supervisor website
answered 2 days ago
mohammad zein
8612
answered 2 days ago
mohammad zein
8612
answered 2 days ago
mohammad zein
8612
answered 2 days ago
mohammad zein
8612
8612
add a comment |
add a comment |
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
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53238770%2fsystem-cron-not-running-intended-process-scheduled-for-execution%23new-answer', 'question_page');
}
);
Post as a guest
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
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
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
Have you tried using
foreverfor auto-start of your node app? npmjs.com/package/forever– ssemilla
Nov 10 at 13:24
Did you check the logs in
/var/log/syslog?– Samarth
Nov 10 at 14:49
After trying multiple options this solution works for me. Declaring PATH and SHELL in cron. I am using /bin/bash So explicitly adding these two solve this issue. @Samarth yes syslogs list script execution indeed.
– Jai Narayan Singh
2 days ago
@ssemilla Although I didn't tried this node tool but using forever in CLI mode good alternative.
– Jai Narayan Singh
2 days ago