Btukfyl

I tried created a very simple cron task that echo's "Hello World" into a file named /tmp/example.txt.

You can see from the screenshot, I tried:

28 23 * * * echo "Hello World" >> /tmp/example.txt



28 23 * * * root /bin/bash echo "Hello World" >> /tmp/example.txt

Also in the screenshot, you can see the date. I have also tried getting the exact date in the cron task (e.g.: 28 23 29 11 4), but that didn't work either.

I also tried using an actual file

28 23 * * * ./pingstuff

The pingstuff file just pings Google. I can run this file and it executes properly. But, when I try using it in the crontab -e, nothing happens at the scheduled time. (Times have been changed accordingly after each attempt.)

I am logged in as a super user. I have permissions to read/write/execute all of these files. I'm not really sure what I'm doing wrong.

A cronjob may fail to execute because

• the cron daemon is not running


• there's a syntax error in the crontab


• there's a syntax error in the command


• or there's a permission problem (e.g. execute bit not set)

To check if the daemon is running, try service cron status or systemctl status cron (the service manager depends on your distribution). The daemon may also be called something slightly different, like crond or cronie.

If it's not running, start it (replace status with start).

If it's running, proceed to check the relevant log files to see whether the job was actually run. Depending on your distribution, this might be logged to /var/log/syslog, /var/log/messages, a daemon-specific file like /var/log/cron, or a systemd binary log file (journalctl -u cron to view). You should see a line for each execution of the job.

When testing crontabs, set an execution time that's more than one minute in the future. Some cron implementations "pre-plan" what tasks to run, i.e. they'll decide at 12:33:00 what to run at 12:34:00, so you'll miss the window of opportunity if you add a 34 12 … cronjob at 12:33:30.

If the job runs but doesn't produce the expected result, try running the command from the crontab manually, as the same user, with the same shell (usually the minimalistic /bin/sh).

One common pitfall (though not the case here) are % characters in the command: they are treated specially by cron and need to be escaped (%) to be seen by the actual command invocation.

Most cron implementations also send the output (if any) of each cronjob as an email. If you haven't set up mail delivery over the internet, those mails should be stored locally and be readable using the mail command.

Your biggest problem is that /bin/bash echo "Hello World"
is not a valid command. 
It looks for a script called echo. 
Try /bin/bash -c 'echo "Hello World"' instead.

The second problem is that you should specify an absolute pathname
for pingstuff.

A third issue that caught my eye is that /tmp/example.txt
already exists (the cat command didn't get an error message). 
Are you sure that you have write permission to it? 
(Of course, that shouldn't be an issue if you're running as root.)

See also Ubuntu 14.04, 16.04, 18.04 Cron job doesn't execute,
although it probably isn't related.