I want to verify that my cron job is executing and at what time. I believe there is a log for my sudo crontab -e jobs, but where?

I searched google and found recommendations to look in /var/log (in which I do not see anything with 'cron' in the name) and to edit the file /etc/syslog.conf which I also do not have.

11 Answers 11


On a default installation the cron jobs get logged to


You can see just cron jobs in that logfile by running

 grep CRON /var/log/syslog

If you haven't reconfigured anything,the entries will be in there.

| improve this answer | |
  • 60
    If there is no MTA installed, cron just throws the job output away. – Barry Kelly Nov 18 '13 at 23:19
  • 15
    The cron log may be in another file in the /var/log/ directory. Check for cron.log or equivalent. – Navigatron Jan 31 '14 at 10:21
  • 9
    this doesn't give me output from the job. it just gives a generic message that the cron was processed. – chovy Dec 12 '15 at 0:34
  • 4
    on AWS it was /var/log/cron – tsukimi Feb 4 '17 at 1:23
  • 6
    @shadi you could also grep -i CRON to search case-insensitive – nafg Apr 24 '17 at 2:08

You can create a cron.log file to contain just the CRON entries that show up in syslog. Note that CRON jobs will still show up in syslog if you follow the following directions.

Open the file


Find the line that starts with:


uncomment that line, save the file, and restart rsyslog:

sudo service rsyslog restart

You should now see a cron log file here:


Cron activity will now be logged to this file (in addition to syslog).

Note that in cron.log you will see entries for when cron ran scripts in /etc/cron.hourly, cron.daily, etc. - e.g. something like:

Apr 12 14:17:01 cd CRON[14368]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

However, you will not see more information about what scripts were actually ran inside /etc/cron.daily or /etc/cron.hourly, unless those scripts direct output to the cron.log (or perhaps to some other log file).

If you want to verify if a crontab is running and not have to search for it in cron.log or syslog, create a crontab that redirects output to a log file of your choice - something like:

01 14 * * * /home/joe/myscript >> /home/log/myscript.log 2>&1

This will redirect all standard output and errors that may be produced by the script that is run to the log file specified.

| improve this answer | |
  • 2
    With my opinion, this answer is better in future. So your syslog file is more clear. – shgnInc Dec 22 '13 at 8:36
  • 9
    To also exclude the cron log from syslog you can change the line *.*;auth,authpriv.none -/var/log/syslog to *.*;auth,authpriv.none,cron.none -/var/log/syslog. – Koen. Feb 13 '14 at 11:35
  • On our CentOS 6, cron.* defined in /etc/rsyslog.conf, whereas i's empty in rsyslog.d folder. – Scott Chu Sep 17 '14 at 3:35
  • what is 2>&1 stand for ? – John Joe Mar 21 '17 at 2:41
  • 3
    @JohnJoe 2>&1 is used to forward stderr to stdout, this way you'll also get stderr to log file. – Sampo Sarrala - codidact.org Jul 25 '17 at 12:38

Sometimes it can be useful to continuously monitor it, in that case:

tail -f /var/log/syslog | grep CRON
| improve this answer | |
  • 17
    Well, you probably want to use -F, which will follow the file across name changes, so that when it gets truncated/moved to, e.g. /var/log/syslog.1.gz, you're still following the current /var/log/syslog file. Per the man docs, this is the same as running tail xxxx -f --retry – Momer Dec 17 '14 at 22:24

You can also direct the output of the individual cronjobs to their own logs for better readability, you will just need to append the output of date somewhere.

 0 15 * * *    /home/andrew/daily-backup.sh >> /var/log/daily-backup.log 2>&1
| improve this answer | |
  • 5
    true, but if this line fails to run due to syntax error, nothing will be written in the output log specified. – Raptor Jul 24 '15 at 2:37
  • 16
    You can solve this by appending 2>&1 after the log file is specified. It is also best practice to test your cronjobs before adding them to the crontab, and then being present for the first scheduled run to ensure that the crontab is properly formatted. – Andrew Meyer Jul 24 '15 at 16:04
  • 3
    If daily-backup.log file doesn't exist, CRON creates it automatically. – Nagabhushan S N Dec 23 '19 at 9:51

If you have systemd installed on your system, you could display cron job log by using the journalctl command.

For example, on my Ubuntu 17.10:

journalctl -u cron.service
| improve this answer | |

This is a very old question, but none of these answers seem satisfactory.

First make your cron job run every minute, then run cron as non-daemon (temporarily, just kill any crond that may have already started) with test logging:

crond -nx test

And see the log of your program execution flowing through your terminal.

| improve this answer | |
  • 10
    Does not run on 14.04 - No command 'crond' found, did you mean: Command 'cron' from package 'cron' (main) – G-. Jul 6 '17 at 9:40
  • Same error on Ubuntu 18.04 today – Nam G VU Apr 25 at 12:30
journalctl -t CROND

From the journalctl manual:

       Show messages for the specified syslog identifier SYSLOG_IDENTIFIER, 
       or for any of the messages with a "SYSLOG_IDENTIFIER" matched by PATTERN.

       This parameter can be specified multiple times.
| improve this answer | |

It is in /var/log/syslog by default.

But it can be set up to create a separate cron.log, which is more useful.

This Q&A describes the process:

16.04: How do I make cron create cron.log and monitor it in real time?

Also in this answer is the instructions to create a wcron command that displays it is near-real-time. Plus, it links to another answer,

How to change cron log level?

that shows how to change the log level to include more than just the start of jobs - level 15 will show errors and end time, also.

| improve this answer | |

Like mentioned earlier, cron jobs get logged to /var/log/syslog

You can pipe the syslog to grep and filter out the CRON logs, like this

less /var/log/syslog | grep CRON 

You can search through your crontab logs, like this

less /var/log/syslog | grep CRON | grep <search-keyword-comes-here>

You can search through your crontab history logs stored in gz files, like this

less /var/log/syslog.2.gz | grep CRON | grep <search-keyword-comes-here>

Its always considered good to have a logging mechanism, you can quickly setup ELK for your servers, you can also experiment with logz .

| improve this answer | |

You could redirect the output of cron to a temporary file. Such as:

00 11 07 * * /bin/bash /home/ubuntu/command.sh > /tmp/output 2>&1

Error and normal output, both will be redirected to the same file

| improve this answer | |

Check all CRON related logs in syslog files included compressed log files as well like this way:

zless /var/log/syslog* | grep CRON
| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.