Crontab fails because shell path not foundScript not running in crontab, file not foundCan't access shell variable in crontab configurationRemoving Prior CrontabsCrontab script not runningCrontab not running entire script?Crontab env variables while using Dockercronjob cannot find environment variables defined in .bashrcCrontab says command not foundcrontab -e does not open the crontab for this userCannot run python script with cron
What does it mean to describe someone as a butt steak?
Stopping power of mountain vs road bike
How can I make my BBEG immortal short of making them a Lich or Vampire?
Infinite Abelian subgroup of infinite non Abelian group example
How to take photos in burst mode, without vibration?
Intersection of two sorted vectors in C++
Why is consensus so controversial in Britain?
Is it possible to run Internet Explorer on OS X El Capitan?
Why is Collection not simply treated as Collection<?>
Why does Kotter return in Welcome Back Kotter
What mechanic is there to disable a threat instead of killing it?
Is the Joker left-handed?
Could gravitational lensing be used to protect a spaceship from a laser?
Do I have a twin with permutated remainders?
Assassin's bullet with mercury
I would say: "You are another teacher", but she is a woman and I am a man
How could indestructible materials be used in power generation?
Doing something right before you need it - expression for this?
Today is the Center
What is the intuition behind short exact sequences of groups; in particular, what is the intuition behind group extensions?
Did Shadowfax go to Valinor?
Brothers & sisters
Western buddy movie with a supernatural twist where a woman turns into an eagle at the end
Does a druid starting with a bow start with no arrows?
Crontab fails because shell path not found
Script not running in crontab, file not foundCan't access shell variable in crontab configurationRemoving Prior CrontabsCrontab script not runningCrontab not running entire script?Crontab env variables while using Dockercronjob cannot find environment variables defined in .bashrcCrontab says command not foundcrontab -e does not open the crontab for this userCannot run python script with cron
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I am looking at the failure output of my crontab.
* * * * * user /usr/bin/python3 /home/user/src/code/prod.py
I get the error /bin/sh: 1: caleb: not found.
This corresponds to
X-Cron-Env: <SHELL=/bin/sh>
which is part of the email the crontab sent me. I created the crontab using
crontab -e
All of it looks like a simple setup is there anything that I am missing?
16.04 cron
New contributor
add a comment |
I am looking at the failure output of my crontab.
* * * * * user /usr/bin/python3 /home/user/src/code/prod.py
I get the error /bin/sh: 1: caleb: not found.
This corresponds to
X-Cron-Env: <SHELL=/bin/sh>
which is part of the email the crontab sent me. I created the crontab using
crontab -e
All of it looks like a simple setup is there anything that I am missing?
16.04 cron
New contributor
3
When you runcrontab -e
it is already using your username so there is no need to add your username to the beginning of the command. The only place on the system that you add the username is in the/etc/crontab
file.
– Terrance
14 hours ago
@Terrance that fixed my problem. i got my solution from cyberciti.biz/faq/… And I looked at the format and paid no attention to the "for system jobs"
– caleb baker
13 hours ago
add a comment |
I am looking at the failure output of my crontab.
* * * * * user /usr/bin/python3 /home/user/src/code/prod.py
I get the error /bin/sh: 1: caleb: not found.
This corresponds to
X-Cron-Env: <SHELL=/bin/sh>
which is part of the email the crontab sent me. I created the crontab using
crontab -e
All of it looks like a simple setup is there anything that I am missing?
16.04 cron
New contributor
I am looking at the failure output of my crontab.
* * * * * user /usr/bin/python3 /home/user/src/code/prod.py
I get the error /bin/sh: 1: caleb: not found.
This corresponds to
X-Cron-Env: <SHELL=/bin/sh>
which is part of the email the crontab sent me. I created the crontab using
crontab -e
All of it looks like a simple setup is there anything that I am missing?
16.04 cron
16.04 cron
New contributor
New contributor
edited 36 mins ago
Community♦
1
1
New contributor
asked 14 hours ago
caleb bakercaleb baker
132
132
New contributor
New contributor
3
When you runcrontab -e
it is already using your username so there is no need to add your username to the beginning of the command. The only place on the system that you add the username is in the/etc/crontab
file.
– Terrance
14 hours ago
@Terrance that fixed my problem. i got my solution from cyberciti.biz/faq/… And I looked at the format and paid no attention to the "for system jobs"
– caleb baker
13 hours ago
add a comment |
3
When you runcrontab -e
it is already using your username so there is no need to add your username to the beginning of the command. The only place on the system that you add the username is in the/etc/crontab
file.
– Terrance
14 hours ago
@Terrance that fixed my problem. i got my solution from cyberciti.biz/faq/… And I looked at the format and paid no attention to the "for system jobs"
– caleb baker
13 hours ago
3
3
When you run
crontab -e
it is already using your username so there is no need to add your username to the beginning of the command. The only place on the system that you add the username is in the /etc/crontab
file.– Terrance
14 hours ago
When you run
crontab -e
it is already using your username so there is no need to add your username to the beginning of the command. The only place on the system that you add the username is in the /etc/crontab
file.– Terrance
14 hours ago
@Terrance that fixed my problem. i got my solution from cyberciti.biz/faq/… And I looked at the format and paid no attention to the "for system jobs"
– caleb baker
13 hours ago
@Terrance that fixed my problem. i got my solution from cyberciti.biz/faq/… And I looked at the format and paid no attention to the "for system jobs"
– caleb baker
13 hours ago
add a comment |
1 Answer
1
active
oldest
votes
If you are using crontab -e
that set of Cron tasks runs as the user which crontab -e
was executed as - that is, your user user
.
Therefore, you should only provide the cron entry WITHOUT the user bits, i.e.:
* * * * * /usr/bin/python3 /home/user/src/code/prod.py
The user
definition you were attempting to use should only be used in the system crontab
in /etc/crontab
and in entries in cron definitions under /etc/cron.d/
.
Not to nitpick, but the "cron user" probably has/usr/bin
in its $PATH. So,* * * * * python3 /home/user/src/code/prod.py
will probably work.
– Seamus
13 hours ago
2
@Seamus when using crontabs it's generally better to use full paths just to rule out that problem.
– Thomas Ward♦
13 hours ago
It's redundant... but I suppose that could be considered "generally better", for some. I'm only trying to point out that the "cron user" does have an environment, and it can be determined if it's not known.
– Seamus
13 hours ago
1
@Seamus I often have to explain to people why their jobs that run fine from a bash prompt don't work correctly under cron (or Autosys etc.). I tell them that it's best to use the full path to everything they can, and explicitly set PATH= what they want it to be, rather than rely on "probably".
– Monty Harder
10 hours ago
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
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
);
);
caleb baker is a new contributor. Be nice, and check out our Code of Conduct.
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%2faskubuntu.com%2fquestions%2f1131213%2fcrontab-fails-because-shell-path-not-found%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you are using crontab -e
that set of Cron tasks runs as the user which crontab -e
was executed as - that is, your user user
.
Therefore, you should only provide the cron entry WITHOUT the user bits, i.e.:
* * * * * /usr/bin/python3 /home/user/src/code/prod.py
The user
definition you were attempting to use should only be used in the system crontab
in /etc/crontab
and in entries in cron definitions under /etc/cron.d/
.
Not to nitpick, but the "cron user" probably has/usr/bin
in its $PATH. So,* * * * * python3 /home/user/src/code/prod.py
will probably work.
– Seamus
13 hours ago
2
@Seamus when using crontabs it's generally better to use full paths just to rule out that problem.
– Thomas Ward♦
13 hours ago
It's redundant... but I suppose that could be considered "generally better", for some. I'm only trying to point out that the "cron user" does have an environment, and it can be determined if it's not known.
– Seamus
13 hours ago
1
@Seamus I often have to explain to people why their jobs that run fine from a bash prompt don't work correctly under cron (or Autosys etc.). I tell them that it's best to use the full path to everything they can, and explicitly set PATH= what they want it to be, rather than rely on "probably".
– Monty Harder
10 hours ago
add a comment |
If you are using crontab -e
that set of Cron tasks runs as the user which crontab -e
was executed as - that is, your user user
.
Therefore, you should only provide the cron entry WITHOUT the user bits, i.e.:
* * * * * /usr/bin/python3 /home/user/src/code/prod.py
The user
definition you were attempting to use should only be used in the system crontab
in /etc/crontab
and in entries in cron definitions under /etc/cron.d/
.
Not to nitpick, but the "cron user" probably has/usr/bin
in its $PATH. So,* * * * * python3 /home/user/src/code/prod.py
will probably work.
– Seamus
13 hours ago
2
@Seamus when using crontabs it's generally better to use full paths just to rule out that problem.
– Thomas Ward♦
13 hours ago
It's redundant... but I suppose that could be considered "generally better", for some. I'm only trying to point out that the "cron user" does have an environment, and it can be determined if it's not known.
– Seamus
13 hours ago
1
@Seamus I often have to explain to people why their jobs that run fine from a bash prompt don't work correctly under cron (or Autosys etc.). I tell them that it's best to use the full path to everything they can, and explicitly set PATH= what they want it to be, rather than rely on "probably".
– Monty Harder
10 hours ago
add a comment |
If you are using crontab -e
that set of Cron tasks runs as the user which crontab -e
was executed as - that is, your user user
.
Therefore, you should only provide the cron entry WITHOUT the user bits, i.e.:
* * * * * /usr/bin/python3 /home/user/src/code/prod.py
The user
definition you were attempting to use should only be used in the system crontab
in /etc/crontab
and in entries in cron definitions under /etc/cron.d/
.
If you are using crontab -e
that set of Cron tasks runs as the user which crontab -e
was executed as - that is, your user user
.
Therefore, you should only provide the cron entry WITHOUT the user bits, i.e.:
* * * * * /usr/bin/python3 /home/user/src/code/prod.py
The user
definition you were attempting to use should only be used in the system crontab
in /etc/crontab
and in entries in cron definitions under /etc/cron.d/
.
edited 13 hours ago
answered 14 hours ago
Thomas Ward♦Thomas Ward
45.1k23125178
45.1k23125178
Not to nitpick, but the "cron user" probably has/usr/bin
in its $PATH. So,* * * * * python3 /home/user/src/code/prod.py
will probably work.
– Seamus
13 hours ago
2
@Seamus when using crontabs it's generally better to use full paths just to rule out that problem.
– Thomas Ward♦
13 hours ago
It's redundant... but I suppose that could be considered "generally better", for some. I'm only trying to point out that the "cron user" does have an environment, and it can be determined if it's not known.
– Seamus
13 hours ago
1
@Seamus I often have to explain to people why their jobs that run fine from a bash prompt don't work correctly under cron (or Autosys etc.). I tell them that it's best to use the full path to everything they can, and explicitly set PATH= what they want it to be, rather than rely on "probably".
– Monty Harder
10 hours ago
add a comment |
Not to nitpick, but the "cron user" probably has/usr/bin
in its $PATH. So,* * * * * python3 /home/user/src/code/prod.py
will probably work.
– Seamus
13 hours ago
2
@Seamus when using crontabs it's generally better to use full paths just to rule out that problem.
– Thomas Ward♦
13 hours ago
It's redundant... but I suppose that could be considered "generally better", for some. I'm only trying to point out that the "cron user" does have an environment, and it can be determined if it's not known.
– Seamus
13 hours ago
1
@Seamus I often have to explain to people why their jobs that run fine from a bash prompt don't work correctly under cron (or Autosys etc.). I tell them that it's best to use the full path to everything they can, and explicitly set PATH= what they want it to be, rather than rely on "probably".
– Monty Harder
10 hours ago
Not to nitpick, but the "cron user" probably has
/usr/bin
in its $PATH. So, * * * * * python3 /home/user/src/code/prod.py
will probably work.– Seamus
13 hours ago
Not to nitpick, but the "cron user" probably has
/usr/bin
in its $PATH. So, * * * * * python3 /home/user/src/code/prod.py
will probably work.– Seamus
13 hours ago
2
2
@Seamus when using crontabs it's generally better to use full paths just to rule out that problem.
– Thomas Ward♦
13 hours ago
@Seamus when using crontabs it's generally better to use full paths just to rule out that problem.
– Thomas Ward♦
13 hours ago
It's redundant... but I suppose that could be considered "generally better", for some. I'm only trying to point out that the "cron user" does have an environment, and it can be determined if it's not known.
– Seamus
13 hours ago
It's redundant... but I suppose that could be considered "generally better", for some. I'm only trying to point out that the "cron user" does have an environment, and it can be determined if it's not known.
– Seamus
13 hours ago
1
1
@Seamus I often have to explain to people why their jobs that run fine from a bash prompt don't work correctly under cron (or Autosys etc.). I tell them that it's best to use the full path to everything they can, and explicitly set PATH= what they want it to be, rather than rely on "probably".
– Monty Harder
10 hours ago
@Seamus I often have to explain to people why their jobs that run fine from a bash prompt don't work correctly under cron (or Autosys etc.). I tell them that it's best to use the full path to everything they can, and explicitly set PATH= what they want it to be, rather than rely on "probably".
– Monty Harder
10 hours ago
add a comment |
caleb baker is a new contributor. Be nice, and check out our Code of Conduct.
caleb baker is a new contributor. Be nice, and check out our Code of Conduct.
caleb baker is a new contributor. Be nice, and check out our Code of Conduct.
caleb baker is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1131213%2fcrontab-fails-because-shell-path-not-found%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
3
When you run
crontab -e
it is already using your username so there is no need to add your username to the beginning of the command. The only place on the system that you add the username is in the/etc/crontab
file.– Terrance
14 hours ago
@Terrance that fixed my problem. i got my solution from cyberciti.biz/faq/… And I looked at the format and paid no attention to the "for system jobs"
– caleb baker
13 hours ago