running bash script from cron job not working properly












0















I have the following script:





#!/bin/bash
echo "$(date +"%r")"

if [ "$FOLDER_ID" != "0" ]
then
node /sync.js -d $FOLDER_ID -l /Downloads
fi




I'm using docker container and I have passed the env variable FOLDER_ID when started the container. This variable supposed to be set when starting the docker container by passing it as ENV.



When I run this script, the node command runs as expected, but when the cron job runs the script, it prints the date at but doesn't execute the node command correctly (I think the issue is related to the $FOLDER_ID variable).



Any suggestions?
Thanks










share|improve this question









New contributor




ialqwaiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • I can't let it pass without commenting: echo "$(date +"%r")" is just a long way of saying date +%r. Separately, I don't suppose FOLDER_ID has any spaces or tabs in it?

    – Jeff Schaller
    1 hour ago











  • no it does not. I can use FOLDER_ID in the commandline with no problems

    – ialqwaiz
    1 hour ago











  • another common problem with cron jobs is that they (as you've seen) run with a new, bare, environment. Are there any other environment variables (perhaps related to the 'node' command or your script) that are also missing?

    – Jeff Schaller
    1 hour ago











  • Yes. I have two different folder_id variables and I have the same issue with the second part of the script. I assumed I didn't use the env variables correctly...

    – ialqwaiz
    1 hour ago
















0















I have the following script:





#!/bin/bash
echo "$(date +"%r")"

if [ "$FOLDER_ID" != "0" ]
then
node /sync.js -d $FOLDER_ID -l /Downloads
fi




I'm using docker container and I have passed the env variable FOLDER_ID when started the container. This variable supposed to be set when starting the docker container by passing it as ENV.



When I run this script, the node command runs as expected, but when the cron job runs the script, it prints the date at but doesn't execute the node command correctly (I think the issue is related to the $FOLDER_ID variable).



Any suggestions?
Thanks










share|improve this question









New contributor




ialqwaiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • I can't let it pass without commenting: echo "$(date +"%r")" is just a long way of saying date +%r. Separately, I don't suppose FOLDER_ID has any spaces or tabs in it?

    – Jeff Schaller
    1 hour ago











  • no it does not. I can use FOLDER_ID in the commandline with no problems

    – ialqwaiz
    1 hour ago











  • another common problem with cron jobs is that they (as you've seen) run with a new, bare, environment. Are there any other environment variables (perhaps related to the 'node' command or your script) that are also missing?

    – Jeff Schaller
    1 hour ago











  • Yes. I have two different folder_id variables and I have the same issue with the second part of the script. I assumed I didn't use the env variables correctly...

    – ialqwaiz
    1 hour ago














0












0








0








I have the following script:





#!/bin/bash
echo "$(date +"%r")"

if [ "$FOLDER_ID" != "0" ]
then
node /sync.js -d $FOLDER_ID -l /Downloads
fi




I'm using docker container and I have passed the env variable FOLDER_ID when started the container. This variable supposed to be set when starting the docker container by passing it as ENV.



When I run this script, the node command runs as expected, but when the cron job runs the script, it prints the date at but doesn't execute the node command correctly (I think the issue is related to the $FOLDER_ID variable).



Any suggestions?
Thanks










share|improve this question









New contributor




ialqwaiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I have the following script:





#!/bin/bash
echo "$(date +"%r")"

if [ "$FOLDER_ID" != "0" ]
then
node /sync.js -d $FOLDER_ID -l /Downloads
fi




I'm using docker container and I have passed the env variable FOLDER_ID when started the container. This variable supposed to be set when starting the docker container by passing it as ENV.



When I run this script, the node command runs as expected, but when the cron job runs the script, it prints the date at but doesn't execute the node command correctly (I think the issue is related to the $FOLDER_ID variable).



Any suggestions?
Thanks







bash cron






share|improve this question









New contributor




ialqwaiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




ialqwaiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 1 hour ago







ialqwaiz













New contributor




ialqwaiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 1 hour ago









ialqwaizialqwaiz

11




11




New contributor




ialqwaiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





ialqwaiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






ialqwaiz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • I can't let it pass without commenting: echo "$(date +"%r")" is just a long way of saying date +%r. Separately, I don't suppose FOLDER_ID has any spaces or tabs in it?

    – Jeff Schaller
    1 hour ago











  • no it does not. I can use FOLDER_ID in the commandline with no problems

    – ialqwaiz
    1 hour ago











  • another common problem with cron jobs is that they (as you've seen) run with a new, bare, environment. Are there any other environment variables (perhaps related to the 'node' command or your script) that are also missing?

    – Jeff Schaller
    1 hour ago











  • Yes. I have two different folder_id variables and I have the same issue with the second part of the script. I assumed I didn't use the env variables correctly...

    – ialqwaiz
    1 hour ago



















  • I can't let it pass without commenting: echo "$(date +"%r")" is just a long way of saying date +%r. Separately, I don't suppose FOLDER_ID has any spaces or tabs in it?

    – Jeff Schaller
    1 hour ago











  • no it does not. I can use FOLDER_ID in the commandline with no problems

    – ialqwaiz
    1 hour ago











  • another common problem with cron jobs is that they (as you've seen) run with a new, bare, environment. Are there any other environment variables (perhaps related to the 'node' command or your script) that are also missing?

    – Jeff Schaller
    1 hour ago











  • Yes. I have two different folder_id variables and I have the same issue with the second part of the script. I assumed I didn't use the env variables correctly...

    – ialqwaiz
    1 hour ago

















I can't let it pass without commenting: echo "$(date +"%r")" is just a long way of saying date +%r. Separately, I don't suppose FOLDER_ID has any spaces or tabs in it?

– Jeff Schaller
1 hour ago





I can't let it pass without commenting: echo "$(date +"%r")" is just a long way of saying date +%r. Separately, I don't suppose FOLDER_ID has any spaces or tabs in it?

– Jeff Schaller
1 hour ago













no it does not. I can use FOLDER_ID in the commandline with no problems

– ialqwaiz
1 hour ago





no it does not. I can use FOLDER_ID in the commandline with no problems

– ialqwaiz
1 hour ago













another common problem with cron jobs is that they (as you've seen) run with a new, bare, environment. Are there any other environment variables (perhaps related to the 'node' command or your script) that are also missing?

– Jeff Schaller
1 hour ago





another common problem with cron jobs is that they (as you've seen) run with a new, bare, environment. Are there any other environment variables (perhaps related to the 'node' command or your script) that are also missing?

– Jeff Schaller
1 hour ago













Yes. I have two different folder_id variables and I have the same issue with the second part of the script. I assumed I didn't use the env variables correctly...

– ialqwaiz
1 hour ago





Yes. I have two different folder_id variables and I have the same issue with the second part of the script. I assumed I didn't use the env variables correctly...

– ialqwaiz
1 hour ago










0






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
});


}
});






ialqwaiz is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505249%2frunning-bash-script-from-cron-job-not-working-properly%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








ialqwaiz is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















ialqwaiz is a new contributor. Be nice, and check out our Code of Conduct.













ialqwaiz is a new contributor. Be nice, and check out our Code of Conduct.












ialqwaiz is a new contributor. Be nice, and check out our Code of Conduct.
















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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505249%2frunning-bash-script-from-cron-job-not-working-properly%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

CARDNET

Boot-repair Failure: Unable to locate package grub-common:i386

濃尾地震