Crontab problem in ubuntu 1804
Clash Royale CLAN TAG#URR8PPP
I'm having problem getting my crontab to work in my ubuntu server 18.04 running as a amazon ec2 instance.
I have the following line in my /etc/crontab file:
*/15 * * * * root /bin/bash /home/ubuntu/gzip/over_time_compile_ec2.sh
But it does not seem to work, and when running sudo service cron status i get the following:
Feb 14 22:20:01 ip-172-31-15-110 CRON[15880]: pam_unix(cron:session): session opened for user ubuntu by (uid=0)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15879]: pam_unix(cron:session): session opened for user root by (uid=0)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15881]: pam_unix(cron:session): session opened for user root by (uid=0)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15882]: (root) CMD (/home/ubuntu/gzip/compile_script.sh)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15883]: (ubuntu) CMD (/home/ubuntu/gzip/compile_script.sh)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15884]: (root) CMD (/bin/bash /home/ubuntu/gzip/over_time_compile_ec2.sh)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15881]: (CRON) info (No MTA installed, discarding output)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15881]: pam_unix(cron:session): session closed for user root
Feb 14 22:20:01 ip-172-31-15-110 CRON[15880]: (CRON) info (No MTA installed, discarding output)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15880]: pam_unix(cron:session): session closed for user ubuntu
I see the line (CRON) info (No MTA installed, discarding output), but it should not make my CRON fail right?
ubuntu cron
asked Feb 14 at 22:30
emilrnemilrn
33
add a comment |
I'm having problem getting my crontab to work in my ubuntu server 18.04 running as a amazon ec2 instance.
I have the following line in my /etc/crontab file:
*/15 * * * * root /bin/bash /home/ubuntu/gzip/over_time_compile_ec2.sh
But it does not seem to work, and when running sudo service cron status i get the following:
Feb 14 22:20:01 ip-172-31-15-110 CRON[15880]: pam_unix(cron:session): session opened for user ubuntu by (uid=0)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15879]: pam_unix(cron:session): session opened for user root by (uid=0)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15881]: pam_unix(cron:session): session opened for user root by (uid=0)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15882]: (root) CMD (/home/ubuntu/gzip/compile_script.sh)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15883]: (ubuntu) CMD (/home/ubuntu/gzip/compile_script.sh)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15884]: (root) CMD (/bin/bash /home/ubuntu/gzip/over_time_compile_ec2.sh)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15881]: (CRON) info (No MTA installed, discarding output)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15881]: pam_unix(cron:session): session closed for user root
Feb 14 22:20:01 ip-172-31-15-110 CRON[15880]: (CRON) info (No MTA installed, discarding output)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15880]: pam_unix(cron:session): session closed for user ubuntu
I see the line (CRON) info (No MTA installed, discarding output), but it should not make my CRON fail right?
ubuntu cron
asked Feb 14 at 22:30
emilrnemilrn
33
It's telling you that the script tried to write something, but that there was nowhere for it to go. What you don't know at this point is whether that was an error message (which might explain why it's presumably not working) or something else. I would recommend you append something like>/tmp/otce.log 2>&1to the end of yourcrontabentry and take a look inside that file after the next 15 minute cycle.
– roaima
Feb 14 at 22:33
add a comment |
I'm having problem getting my crontab to work in my ubuntu server 18.04 running as a amazon ec2 instance.
I have the following line in my /etc/crontab file:
*/15 * * * * root /bin/bash /home/ubuntu/gzip/over_time_compile_ec2.sh
But it does not seem to work, and when running sudo service cron status i get the following:
Feb 14 22:20:01 ip-172-31-15-110 CRON[15880]: pam_unix(cron:session): session opened for user ubuntu by (uid=0)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15879]: pam_unix(cron:session): session opened for user root by (uid=0)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15881]: pam_unix(cron:session): session opened for user root by (uid=0)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15882]: (root) CMD (/home/ubuntu/gzip/compile_script.sh)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15883]: (ubuntu) CMD (/home/ubuntu/gzip/compile_script.sh)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15884]: (root) CMD (/bin/bash /home/ubuntu/gzip/over_time_compile_ec2.sh)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15881]: (CRON) info (No MTA installed, discarding output)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15881]: pam_unix(cron:session): session closed for user root
Feb 14 22:20:01 ip-172-31-15-110 CRON[15880]: (CRON) info (No MTA installed, discarding output)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15880]: pam_unix(cron:session): session closed for user ubuntu
I see the line (CRON) info (No MTA installed, discarding output), but it should not make my CRON fail right?
ubuntu cron
asked Feb 14 at 22:30
emilrnemilrn
33
I'm having problem getting my crontab to work in my ubuntu server 18.04 running as a amazon ec2 instance.
I have the following line in my /etc/crontab file:
*/15 * * * * root /bin/bash /home/ubuntu/gzip/over_time_compile_ec2.sh
But it does not seem to work, and when running sudo service cron status i get the following:
Feb 14 22:20:01 ip-172-31-15-110 CRON[15880]: pam_unix(cron:session): session opened for user ubuntu by (uid=0)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15879]: pam_unix(cron:session): session opened for user root by (uid=0)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15881]: pam_unix(cron:session): session opened for user root by (uid=0)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15882]: (root) CMD (/home/ubuntu/gzip/compile_script.sh)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15883]: (ubuntu) CMD (/home/ubuntu/gzip/compile_script.sh)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15884]: (root) CMD (/bin/bash /home/ubuntu/gzip/over_time_compile_ec2.sh)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15881]: (CRON) info (No MTA installed, discarding output)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15881]: pam_unix(cron:session): session closed for user root
Feb 14 22:20:01 ip-172-31-15-110 CRON[15880]: (CRON) info (No MTA installed, discarding output)
Feb 14 22:20:01 ip-172-31-15-110 CRON[15880]: pam_unix(cron:session): session closed for user ubuntu
I see the line (CRON) info (No MTA installed, discarding output), but it should not make my CRON fail right?
ubuntu cron
ubuntu cron
asked Feb 14 at 22:30
emilrnemilrn
33
asked Feb 14 at 22:30
emilrnemilrn
33
asked Feb 14 at 22:30
emilrnemilrn
33
asked Feb 14 at 22:30
emilrnemilrn
33
asked Feb 14 at 22:30
emilrnemilrn
33
33
It's telling you that the script tried to write something, but that there was nowhere for it to go. What you don't know at this point is whether that was an error message (which might explain why it's presumably not working) or something else. I would recommend you append something like>/tmp/otce.log 2>&1to the end of yourcrontabentry and take a look inside that file after the next 15 minute cycle.
– roaima
Feb 14 at 22:33
add a comment |
It's telling you that the script tried to write something, but that there was nowhere for it to go. What you don't know at this point is whether that was an error message (which might explain why it's presumably not working) or something else. I would recommend you append something like>/tmp/otce.log 2>&1to the end of yourcrontabentry and take a look inside that file after the next 15 minute cycle.
– roaima
Feb 14 at 22:33
It's telling you that the script tried to write something, but that there was nowhere for it to go. What you don't know at this point is whether that was an error message (which might explain why it's presumably not working) or something else. I would recommend you append something like
>/tmp/otce.log 2>&1 to the end of your crontab entry and take a look inside that file after the next 15 minute cycle.– roaima
Feb 14 at 22:33
It's telling you that the script tried to write something, but that there was nowhere for it to go. What you don't know at this point is whether that was an error message (which might explain why it's presumably not working) or something else. I would recommend you append something like
>/tmp/otce.log 2>&1 to the end of your crontab entry and take a look inside that file after the next 15 minute cycle.– roaima
Feb 14 at 22:33
add a comment |
2 Answers
2
active
oldest
votes
Having no MTA (like postfix or similar) installed will not make your cron job fail, but it prevents cron from sending the owner of the job any output of the job via email.
If the job failed (for any reason), or produced output, you would not get notified about it and that information would be discarded.
If you don't want to install an MTA, use a redirection of the script to a log file:
*/15 * * * * root /bin/bash /home/ubuntu/gzip/over_time_compile_ec2.sh >/tmp/job.out 2>/tmp/job.err
This would put standard output messages in /tmp/job.out and any diagnostic messages that the script generates into /tmp/job.err. You may also redirect both types of messages into the same file with >/tmp/job.out 2>&1.
With >, these files would be emptied and rewritten each time the job runs. With >>, the files would be appended to (but leave 2>&1 as is, if you redirect to the same file; 2>>&1 would not work).
answered Feb 14 at 22:37
KusalanandaKusalananda
135k17255419
Thanks, just to clarify, you are sure there is nothing wrong with the syntax or layout in the crontab file?
– emilrn
Feb 14 at 22:41
@emilrn The syntax looks correct for the system crontab file in/etc/crontab. In a user's crontab file edited viacrontab -e, the 6th field (with the username) should not be there.
– Kusalananda
Feb 14 at 22:42
@emilrn You can also see that the log says that it's actually running the correct command, your script. So the cron side of things work. You just have to capture the output of the actual script to see what's going on.
– Kusalananda
Feb 14 at 22:47
I often use what I call poor man's logrotate for such cronjobs:*/15 * * * * root /bin/bash … 1>/tmp/job-$(date '+%M').out 2>&1This will create logfiles with the current minute in their name. Because the job runs every 15 minutes you'll have 4 logfiles (job-00.out,job-15.out, ...) and no housekeeping is needed. If you use$(date '+%H%M')instead (hour, minute) you'll have 24*4=96 files for one day and they overwrite themselves after a day in a round-robin fashion.
– PerlDuck
Feb 15 at 10:32
add a comment |
In my file over_time_compile_ec2.sh there were a path to another script as cron were in the current directory, as it was not.
So i just added the full path over the other script.
edited Feb 14 at 23:45
Rui F Ribeiro
41.4k1481140
answered Feb 14 at 22:58
emilrnemilrn
33
add a comment |
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
);
);
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%2f500733%2fcrontab-problem-in-ubuntu-1804%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Having no MTA (like postfix or similar) installed will not make your cron job fail, but it prevents cron from sending the owner of the job any output of the job via email.
If the job failed (for any reason), or produced output, you would not get notified about it and that information would be discarded.
If you don't want to install an MTA, use a redirection of the script to a log file:
*/15 * * * * root /bin/bash /home/ubuntu/gzip/over_time_compile_ec2.sh >/tmp/job.out 2>/tmp/job.err
This would put standard output messages in /tmp/job.out and any diagnostic messages that the script generates into /tmp/job.err. You may also redirect both types of messages into the same file with >/tmp/job.out 2>&1.
With >, these files would be emptied and rewritten each time the job runs. With >>, the files would be appended to (but leave 2>&1 as is, if you redirect to the same file; 2>>&1 would not work).
answered Feb 14 at 22:37
KusalanandaKusalananda
135k17255419
Thanks, just to clarify, you are sure there is nothing wrong with the syntax or layout in the crontab file?
– emilrn
Feb 14 at 22:41
@emilrn The syntax looks correct for the system crontab file in/etc/crontab. In a user's crontab file edited viacrontab -e, the 6th field (with the username) should not be there.
– Kusalananda
Feb 14 at 22:42
@emilrn You can also see that the log says that it's actually running the correct command, your script. So the cron side of things work. You just have to capture the output of the actual script to see what's going on.
– Kusalananda
Feb 14 at 22:47
I often use what I call poor man's logrotate for such cronjobs:*/15 * * * * root /bin/bash … 1>/tmp/job-$(date '+%M').out 2>&1This will create logfiles with the current minute in their name. Because the job runs every 15 minutes you'll have 4 logfiles (job-00.out,job-15.out, ...) and no housekeeping is needed. If you use$(date '+%H%M')instead (hour, minute) you'll have 24*4=96 files for one day and they overwrite themselves after a day in a round-robin fashion.
– PerlDuck
Feb 15 at 10:32
add a comment |
Having no MTA (like postfix or similar) installed will not make your cron job fail, but it prevents cron from sending the owner of the job any output of the job via email.
If the job failed (for any reason), or produced output, you would not get notified about it and that information would be discarded.
If you don't want to install an MTA, use a redirection of the script to a log file:
*/15 * * * * root /bin/bash /home/ubuntu/gzip/over_time_compile_ec2.sh >/tmp/job.out 2>/tmp/job.err
This would put standard output messages in /tmp/job.out and any diagnostic messages that the script generates into /tmp/job.err. You may also redirect both types of messages into the same file with >/tmp/job.out 2>&1.
With >, these files would be emptied and rewritten each time the job runs. With >>, the files would be appended to (but leave 2>&1 as is, if you redirect to the same file; 2>>&1 would not work).
answered Feb 14 at 22:37
KusalanandaKusalananda
135k17255419
Thanks, just to clarify, you are sure there is nothing wrong with the syntax or layout in the crontab file?
– emilrn
Feb 14 at 22:41
@emilrn The syntax looks correct for the system crontab file in/etc/crontab. In a user's crontab file edited viacrontab -e, the 6th field (with the username) should not be there.
– Kusalananda
Feb 14 at 22:42
@emilrn You can also see that the log says that it's actually running the correct command, your script. So the cron side of things work. You just have to capture the output of the actual script to see what's going on.
– Kusalananda
Feb 14 at 22:47
I often use what I call poor man's logrotate for such cronjobs:*/15 * * * * root /bin/bash … 1>/tmp/job-$(date '+%M').out 2>&1This will create logfiles with the current minute in their name. Because the job runs every 15 minutes you'll have 4 logfiles (job-00.out,job-15.out, ...) and no housekeeping is needed. If you use$(date '+%H%M')instead (hour, minute) you'll have 24*4=96 files for one day and they overwrite themselves after a day in a round-robin fashion.
– PerlDuck
Feb 15 at 10:32
add a comment |
Having no MTA (like postfix or similar) installed will not make your cron job fail, but it prevents cron from sending the owner of the job any output of the job via email.
If the job failed (for any reason), or produced output, you would not get notified about it and that information would be discarded.
If you don't want to install an MTA, use a redirection of the script to a log file:
*/15 * * * * root /bin/bash /home/ubuntu/gzip/over_time_compile_ec2.sh >/tmp/job.out 2>/tmp/job.err
This would put standard output messages in /tmp/job.out and any diagnostic messages that the script generates into /tmp/job.err. You may also redirect both types of messages into the same file with >/tmp/job.out 2>&1.
With >, these files would be emptied and rewritten each time the job runs. With >>, the files would be appended to (but leave 2>&1 as is, if you redirect to the same file; 2>>&1 would not work).
answered Feb 14 at 22:37
KusalanandaKusalananda
135k17255419
Having no MTA (like postfix or similar) installed will not make your cron job fail, but it prevents cron from sending the owner of the job any output of the job via email.
If the job failed (for any reason), or produced output, you would not get notified about it and that information would be discarded.
If you don't want to install an MTA, use a redirection of the script to a log file:
*/15 * * * * root /bin/bash /home/ubuntu/gzip/over_time_compile_ec2.sh >/tmp/job.out 2>/tmp/job.err
This would put standard output messages in /tmp/job.out and any diagnostic messages that the script generates into /tmp/job.err. You may also redirect both types of messages into the same file with >/tmp/job.out 2>&1.
With >, these files would be emptied and rewritten each time the job runs. With >>, the files would be appended to (but leave 2>&1 as is, if you redirect to the same file; 2>>&1 would not work).
answered Feb 14 at 22:37
KusalanandaKusalananda
135k17255419
answered Feb 14 at 22:37
KusalanandaKusalananda
135k17255419
answered Feb 14 at 22:37
KusalanandaKusalananda
135k17255419
answered Feb 14 at 22:37
KusalanandaKusalananda
135k17255419
135k17255419
Thanks, just to clarify, you are sure there is nothing wrong with the syntax or layout in the crontab file?
– emilrn
Feb 14 at 22:41
@emilrn The syntax looks correct for the system crontab file in/etc/crontab. In a user's crontab file edited viacrontab -e, the 6th field (with the username) should not be there.
– Kusalananda
Feb 14 at 22:42
@emilrn You can also see that the log says that it's actually running the correct command, your script. So the cron side of things work. You just have to capture the output of the actual script to see what's going on.
– Kusalananda
Feb 14 at 22:47
I often use what I call poor man's logrotate for such cronjobs:*/15 * * * * root /bin/bash … 1>/tmp/job-$(date '+%M').out 2>&1This will create logfiles with the current minute in their name. Because the job runs every 15 minutes you'll have 4 logfiles (job-00.out,job-15.out, ...) and no housekeeping is needed. If you use$(date '+%H%M')instead (hour, minute) you'll have 24*4=96 files for one day and they overwrite themselves after a day in a round-robin fashion.
– PerlDuck
Feb 15 at 10:32
add a comment |
Thanks, just to clarify, you are sure there is nothing wrong with the syntax or layout in the crontab file?
– emilrn
Feb 14 at 22:41
@emilrn The syntax looks correct for the system crontab file in/etc/crontab. In a user's crontab file edited viacrontab -e, the 6th field (with the username) should not be there.
– Kusalananda
Feb 14 at 22:42
@emilrn You can also see that the log says that it's actually running the correct command, your script. So the cron side of things work. You just have to capture the output of the actual script to see what's going on.
– Kusalananda
Feb 14 at 22:47
I often use what I call poor man's logrotate for such cronjobs:*/15 * * * * root /bin/bash … 1>/tmp/job-$(date '+%M').out 2>&1This will create logfiles with the current minute in their name. Because the job runs every 15 minutes you'll have 4 logfiles (job-00.out,job-15.out, ...) and no housekeeping is needed. If you use$(date '+%H%M')instead (hour, minute) you'll have 24*4=96 files for one day and they overwrite themselves after a day in a round-robin fashion.
– PerlDuck
Feb 15 at 10:32
Thanks, just to clarify, you are sure there is nothing wrong with the syntax or layout in the crontab file?
– emilrn
Feb 14 at 22:41
Thanks, just to clarify, you are sure there is nothing wrong with the syntax or layout in the crontab file?
– emilrn
Feb 14 at 22:41
@emilrn The syntax looks correct for the system crontab file in
/etc/crontab. In a user's crontab file edited via crontab -e, the 6th field (with the username) should not be there.– Kusalananda
Feb 14 at 22:42
@emilrn The syntax looks correct for the system crontab file in
/etc/crontab. In a user's crontab file edited via crontab -e, the 6th field (with the username) should not be there.– Kusalananda
Feb 14 at 22:42
@emilrn You can also see that the log says that it's actually running the correct command, your script. So the cron side of things work. You just have to capture the output of the actual script to see what's going on.
– Kusalananda
Feb 14 at 22:47
@emilrn You can also see that the log says that it's actually running the correct command, your script. So the cron side of things work. You just have to capture the output of the actual script to see what's going on.
– Kusalananda
Feb 14 at 22:47
I often use what I call poor man's logrotate for such cronjobs:
*/15 * * * * root /bin/bash … 1>/tmp/job-$(date '+%M').out 2>&1 This will create logfiles with the current minute in their name. Because the job runs every 15 minutes you'll have 4 logfiles (job-00.out, job-15.out, ...) and no housekeeping is needed. If you use $(date '+%H%M') instead (hour, minute) you'll have 24*4=96 files for one day and they overwrite themselves after a day in a round-robin fashion.– PerlDuck
Feb 15 at 10:32
I often use what I call poor man's logrotate for such cronjobs:
*/15 * * * * root /bin/bash … 1>/tmp/job-$(date '+%M').out 2>&1 This will create logfiles with the current minute in their name. Because the job runs every 15 minutes you'll have 4 logfiles (job-00.out, job-15.out, ...) and no housekeeping is needed. If you use $(date '+%H%M') instead (hour, minute) you'll have 24*4=96 files for one day and they overwrite themselves after a day in a round-robin fashion.– PerlDuck
Feb 15 at 10:32
add a comment |
In my file over_time_compile_ec2.sh there were a path to another script as cron were in the current directory, as it was not.
So i just added the full path over the other script.
edited Feb 14 at 23:45
Rui F Ribeiro
41.4k1481140
answered Feb 14 at 22:58
emilrnemilrn
33
add a comment |
In my file over_time_compile_ec2.sh there were a path to another script as cron were in the current directory, as it was not.
So i just added the full path over the other script.
edited Feb 14 at 23:45
Rui F Ribeiro
41.4k1481140
answered Feb 14 at 22:58
emilrnemilrn
33
add a comment |
In my file over_time_compile_ec2.sh there were a path to another script as cron were in the current directory, as it was not.
So i just added the full path over the other script.
edited Feb 14 at 23:45
Rui F Ribeiro
41.4k1481140
answered Feb 14 at 22:58
emilrnemilrn
33
In my file over_time_compile_ec2.sh there were a path to another script as cron were in the current directory, as it was not.
So i just added the full path over the other script.
edited Feb 14 at 23:45
Rui F Ribeiro
41.4k1481140
answered Feb 14 at 22:58
emilrnemilrn
33
edited Feb 14 at 23:45
Rui F Ribeiro
41.4k1481140
edited Feb 14 at 23:45
Rui F Ribeiro
41.4k1481140
edited Feb 14 at 23:45
Rui F Ribeiro
41.4k1481140
41.4k1481140
answered Feb 14 at 22:58
emilrnemilrn
33
answered Feb 14 at 22:58
emilrnemilrn
33
answered Feb 14 at 22:58
emilrnemilrn
33
33
add a comment |
add a comment |
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.
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%2f500733%2fcrontab-problem-in-ubuntu-1804%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's telling you that the script tried to write something, but that there was nowhere for it to go. What you don't know at this point is whether that was an error message (which might explain why it's presumably not working) or something else. I would recommend you append something like
>/tmp/otce.log 2>&1to the end of yourcrontabentry and take a look inside that file after the next 15 minute cycle.– roaima
Feb 14 at 22:33