Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

18
  • 2
    Please edit your question to include an example crontab entry that isn't working for you. Also, if you've created a simple test script that shows it has been invoked (e.g., creates a file under the home directory of the user whose crontab invoked it), showing that script's failing crontab entry would be very good. Commented Jun 21 at 15:47
  • 3
    That screenshot seems to show your intended script. What about the simple script that shows it was invoked, like the one I described in my previous comment? You're trying to troubleshoot a very basic and simple action: Cron invoking your script. So you want to begin with a very basic and simple script. After you've fixed the cron invocation, you can switch to your intended script, confident that cron will invoke it. (If there are further issues, you can then focus on the construction of the script) Commented Jun 21 at 18:11
  • 1
    Do: sudo zgrep -i cron /var/log/* Commented Jun 21 at 21:19
  • 1
    What does the script look like? Is it using any variables that you set in your interactive shell's startup files? Commented Jun 22 at 14:32
  • 1
    @Kusalananda My bad: it states 'My script calls $date' as I noted in a previous comment. It would be helpful to get responses and evidence from the comments already made. Commented Jun 22 at 14:38