Cron job not executing












2















I'm trying to use cron for the first time, and I'm stuck.



I'm using Ubuntu 10.10, and the following is my /etc/crontab file. The only modification that I've made is appending the last line.



I've verified that cron is running, and the other jobs here run, but the last one does not.



# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file
# and files in /etc/cron.d. These files also have username fields,
# that none of the other crontabs do.

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# m h dom mon dow user command
17 * * * * root cd / && run-parts --report /etc/cron.hourly
25 6 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6 * * 7 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6 1 * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
#
21 22 * * * root /etc/mycron/myscript.sh > /home/me/stuff/log/cron.log


I've checked $ sudo grep CRON /var/log/syslog and found evidence of the hourly jobs, but nothing for the new job.



I've looked for cron.allow and cron.deny files, but they don't seem to exist on my machine.










share|improve this question





























    2















    I'm trying to use cron for the first time, and I'm stuck.



    I'm using Ubuntu 10.10, and the following is my /etc/crontab file. The only modification that I've made is appending the last line.



    I've verified that cron is running, and the other jobs here run, but the last one does not.



    # /etc/crontab: system-wide crontab
    # Unlike any other crontab you don't have to run the `crontab'
    # command to install the new version when you edit this file
    # and files in /etc/cron.d. These files also have username fields,
    # that none of the other crontabs do.

    SHELL=/bin/sh
    PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

    # m h dom mon dow user command
    17 * * * * root cd / && run-parts --report /etc/cron.hourly
    25 6 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
    47 6 * * 7 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
    52 6 1 * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
    #
    21 22 * * * root /etc/mycron/myscript.sh > /home/me/stuff/log/cron.log


    I've checked $ sudo grep CRON /var/log/syslog and found evidence of the hourly jobs, but nothing for the new job.



    I've looked for cron.allow and cron.deny files, but they don't seem to exist on my machine.










    share|improve this question



























      2












      2








      2


      1






      I'm trying to use cron for the first time, and I'm stuck.



      I'm using Ubuntu 10.10, and the following is my /etc/crontab file. The only modification that I've made is appending the last line.



      I've verified that cron is running, and the other jobs here run, but the last one does not.



      # /etc/crontab: system-wide crontab
      # Unlike any other crontab you don't have to run the `crontab'
      # command to install the new version when you edit this file
      # and files in /etc/cron.d. These files also have username fields,
      # that none of the other crontabs do.

      SHELL=/bin/sh
      PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

      # m h dom mon dow user command
      17 * * * * root cd / && run-parts --report /etc/cron.hourly
      25 6 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
      47 6 * * 7 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
      52 6 1 * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
      #
      21 22 * * * root /etc/mycron/myscript.sh > /home/me/stuff/log/cron.log


      I've checked $ sudo grep CRON /var/log/syslog and found evidence of the hourly jobs, but nothing for the new job.



      I've looked for cron.allow and cron.deny files, but they don't seem to exist on my machine.










      share|improve this question
















      I'm trying to use cron for the first time, and I'm stuck.



      I'm using Ubuntu 10.10, and the following is my /etc/crontab file. The only modification that I've made is appending the last line.



      I've verified that cron is running, and the other jobs here run, but the last one does not.



      # /etc/crontab: system-wide crontab
      # Unlike any other crontab you don't have to run the `crontab'
      # command to install the new version when you edit this file
      # and files in /etc/cron.d. These files also have username fields,
      # that none of the other crontabs do.

      SHELL=/bin/sh
      PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

      # m h dom mon dow user command
      17 * * * * root cd / && run-parts --report /etc/cron.hourly
      25 6 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
      47 6 * * 7 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
      52 6 1 * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
      #
      21 22 * * * root /etc/mycron/myscript.sh > /home/me/stuff/log/cron.log


      I've checked $ sudo grep CRON /var/log/syslog and found evidence of the hourly jobs, but nothing for the new job.



      I've looked for cron.allow and cron.deny files, but they don't seem to exist on my machine.







      ubuntu cron






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 6 at 21:27









      Rui F Ribeiro

      39.5k1479132




      39.5k1479132










      asked Sep 6 '11 at 1:43









      Eric WilsonEric Wilson

      1,90672439




      1,90672439






















          1 Answer
          1






          active

          oldest

          votes


















          2














          I hate to ask the obvious, but is /etc/mycron/myscript.sh executable? You can check with:



          ls -l /etc/mycron/myscript.sh


          Should generally see 3 x's. If not, try:



          chmod -V +x /etc/mycron/myscript.sh


          You can also use sh or bash to run the script, using this line in the cron instead:



          sh /etc/mycron/myscript.sh





          share|improve this answer
























          • It is executable, thanks for asking. (Really) I'm curious what difference adding sh makes. (I'm trying it, I just don't have any idea what it could mean if it works.)

            – Eric Wilson
            Sep 6 '11 at 2:02






          • 1





            OK, adding sh made it work. What was cron trying to do when it wasn't there? I'd really appreciate some insight here, otherwise I'll superstitiously add sh to cron jobs indefinitely.

            – Eric Wilson
            Sep 6 '11 at 2:10











          • @EricWilson Cron executes the command through a shell. With a non-executable myscript.sh isn't executable, that shell emits the error message /etc/mycron/myscript.sh: Permission denied and moves on to the next instruction (i.e. exits, since this is the only instruction). The error message is sent through local e-mail to your account, like all output from a cron job. If you haven't installed an MTA, the cron job output is lost.

            – Gilles
            Sep 6 '11 at 7:22











          • @Giles But my script was executable. I had executed it from the command line, and confirmed that all three xs were there.

            – Eric Wilson
            Sep 6 '11 at 10:07











          • How about the shebang? Does the first line say: #!/bin/sh or #!/bin/bash -- this may be your problem.

            – laebshade
            Sep 11 '11 at 21:55













          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


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f20166%2fcron-job-not-executing%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









          2














          I hate to ask the obvious, but is /etc/mycron/myscript.sh executable? You can check with:



          ls -l /etc/mycron/myscript.sh


          Should generally see 3 x's. If not, try:



          chmod -V +x /etc/mycron/myscript.sh


          You can also use sh or bash to run the script, using this line in the cron instead:



          sh /etc/mycron/myscript.sh





          share|improve this answer
























          • It is executable, thanks for asking. (Really) I'm curious what difference adding sh makes. (I'm trying it, I just don't have any idea what it could mean if it works.)

            – Eric Wilson
            Sep 6 '11 at 2:02






          • 1





            OK, adding sh made it work. What was cron trying to do when it wasn't there? I'd really appreciate some insight here, otherwise I'll superstitiously add sh to cron jobs indefinitely.

            – Eric Wilson
            Sep 6 '11 at 2:10











          • @EricWilson Cron executes the command through a shell. With a non-executable myscript.sh isn't executable, that shell emits the error message /etc/mycron/myscript.sh: Permission denied and moves on to the next instruction (i.e. exits, since this is the only instruction). The error message is sent through local e-mail to your account, like all output from a cron job. If you haven't installed an MTA, the cron job output is lost.

            – Gilles
            Sep 6 '11 at 7:22











          • @Giles But my script was executable. I had executed it from the command line, and confirmed that all three xs were there.

            – Eric Wilson
            Sep 6 '11 at 10:07











          • How about the shebang? Does the first line say: #!/bin/sh or #!/bin/bash -- this may be your problem.

            – laebshade
            Sep 11 '11 at 21:55


















          2














          I hate to ask the obvious, but is /etc/mycron/myscript.sh executable? You can check with:



          ls -l /etc/mycron/myscript.sh


          Should generally see 3 x's. If not, try:



          chmod -V +x /etc/mycron/myscript.sh


          You can also use sh or bash to run the script, using this line in the cron instead:



          sh /etc/mycron/myscript.sh





          share|improve this answer
























          • It is executable, thanks for asking. (Really) I'm curious what difference adding sh makes. (I'm trying it, I just don't have any idea what it could mean if it works.)

            – Eric Wilson
            Sep 6 '11 at 2:02






          • 1





            OK, adding sh made it work. What was cron trying to do when it wasn't there? I'd really appreciate some insight here, otherwise I'll superstitiously add sh to cron jobs indefinitely.

            – Eric Wilson
            Sep 6 '11 at 2:10











          • @EricWilson Cron executes the command through a shell. With a non-executable myscript.sh isn't executable, that shell emits the error message /etc/mycron/myscript.sh: Permission denied and moves on to the next instruction (i.e. exits, since this is the only instruction). The error message is sent through local e-mail to your account, like all output from a cron job. If you haven't installed an MTA, the cron job output is lost.

            – Gilles
            Sep 6 '11 at 7:22











          • @Giles But my script was executable. I had executed it from the command line, and confirmed that all three xs were there.

            – Eric Wilson
            Sep 6 '11 at 10:07











          • How about the shebang? Does the first line say: #!/bin/sh or #!/bin/bash -- this may be your problem.

            – laebshade
            Sep 11 '11 at 21:55
















          2












          2








          2







          I hate to ask the obvious, but is /etc/mycron/myscript.sh executable? You can check with:



          ls -l /etc/mycron/myscript.sh


          Should generally see 3 x's. If not, try:



          chmod -V +x /etc/mycron/myscript.sh


          You can also use sh or bash to run the script, using this line in the cron instead:



          sh /etc/mycron/myscript.sh





          share|improve this answer













          I hate to ask the obvious, but is /etc/mycron/myscript.sh executable? You can check with:



          ls -l /etc/mycron/myscript.sh


          Should generally see 3 x's. If not, try:



          chmod -V +x /etc/mycron/myscript.sh


          You can also use sh or bash to run the script, using this line in the cron instead:



          sh /etc/mycron/myscript.sh






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Sep 6 '11 at 1:53









          laebshadelaebshade

          1,7211015




          1,7211015













          • It is executable, thanks for asking. (Really) I'm curious what difference adding sh makes. (I'm trying it, I just don't have any idea what it could mean if it works.)

            – Eric Wilson
            Sep 6 '11 at 2:02






          • 1





            OK, adding sh made it work. What was cron trying to do when it wasn't there? I'd really appreciate some insight here, otherwise I'll superstitiously add sh to cron jobs indefinitely.

            – Eric Wilson
            Sep 6 '11 at 2:10











          • @EricWilson Cron executes the command through a shell. With a non-executable myscript.sh isn't executable, that shell emits the error message /etc/mycron/myscript.sh: Permission denied and moves on to the next instruction (i.e. exits, since this is the only instruction). The error message is sent through local e-mail to your account, like all output from a cron job. If you haven't installed an MTA, the cron job output is lost.

            – Gilles
            Sep 6 '11 at 7:22











          • @Giles But my script was executable. I had executed it from the command line, and confirmed that all three xs were there.

            – Eric Wilson
            Sep 6 '11 at 10:07











          • How about the shebang? Does the first line say: #!/bin/sh or #!/bin/bash -- this may be your problem.

            – laebshade
            Sep 11 '11 at 21:55





















          • It is executable, thanks for asking. (Really) I'm curious what difference adding sh makes. (I'm trying it, I just don't have any idea what it could mean if it works.)

            – Eric Wilson
            Sep 6 '11 at 2:02






          • 1





            OK, adding sh made it work. What was cron trying to do when it wasn't there? I'd really appreciate some insight here, otherwise I'll superstitiously add sh to cron jobs indefinitely.

            – Eric Wilson
            Sep 6 '11 at 2:10











          • @EricWilson Cron executes the command through a shell. With a non-executable myscript.sh isn't executable, that shell emits the error message /etc/mycron/myscript.sh: Permission denied and moves on to the next instruction (i.e. exits, since this is the only instruction). The error message is sent through local e-mail to your account, like all output from a cron job. If you haven't installed an MTA, the cron job output is lost.

            – Gilles
            Sep 6 '11 at 7:22











          • @Giles But my script was executable. I had executed it from the command line, and confirmed that all three xs were there.

            – Eric Wilson
            Sep 6 '11 at 10:07











          • How about the shebang? Does the first line say: #!/bin/sh or #!/bin/bash -- this may be your problem.

            – laebshade
            Sep 11 '11 at 21:55



















          It is executable, thanks for asking. (Really) I'm curious what difference adding sh makes. (I'm trying it, I just don't have any idea what it could mean if it works.)

          – Eric Wilson
          Sep 6 '11 at 2:02





          It is executable, thanks for asking. (Really) I'm curious what difference adding sh makes. (I'm trying it, I just don't have any idea what it could mean if it works.)

          – Eric Wilson
          Sep 6 '11 at 2:02




          1




          1





          OK, adding sh made it work. What was cron trying to do when it wasn't there? I'd really appreciate some insight here, otherwise I'll superstitiously add sh to cron jobs indefinitely.

          – Eric Wilson
          Sep 6 '11 at 2:10





          OK, adding sh made it work. What was cron trying to do when it wasn't there? I'd really appreciate some insight here, otherwise I'll superstitiously add sh to cron jobs indefinitely.

          – Eric Wilson
          Sep 6 '11 at 2:10













          @EricWilson Cron executes the command through a shell. With a non-executable myscript.sh isn't executable, that shell emits the error message /etc/mycron/myscript.sh: Permission denied and moves on to the next instruction (i.e. exits, since this is the only instruction). The error message is sent through local e-mail to your account, like all output from a cron job. If you haven't installed an MTA, the cron job output is lost.

          – Gilles
          Sep 6 '11 at 7:22





          @EricWilson Cron executes the command through a shell. With a non-executable myscript.sh isn't executable, that shell emits the error message /etc/mycron/myscript.sh: Permission denied and moves on to the next instruction (i.e. exits, since this is the only instruction). The error message is sent through local e-mail to your account, like all output from a cron job. If you haven't installed an MTA, the cron job output is lost.

          – Gilles
          Sep 6 '11 at 7:22













          @Giles But my script was executable. I had executed it from the command line, and confirmed that all three xs were there.

          – Eric Wilson
          Sep 6 '11 at 10:07





          @Giles But my script was executable. I had executed it from the command line, and confirmed that all three xs were there.

          – Eric Wilson
          Sep 6 '11 at 10:07













          How about the shebang? Does the first line say: #!/bin/sh or #!/bin/bash -- this may be your problem.

          – laebshade
          Sep 11 '11 at 21:55







          How about the shebang? Does the first line say: #!/bin/sh or #!/bin/bash -- this may be your problem.

          – laebshade
          Sep 11 '11 at 21:55




















          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f20166%2fcron-job-not-executing%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

          Morgemoulin

          Scott Moir

          Souastre