Bad minute in crontab?

--------------------------------------------------
Rise to the top 3% as a developer or hire one of them at Toptal: https://topt.al/25cXVn
--------------------------------------------------

Music by Eric Matyas
https://www.soundimage.org
Track title: Beneath the City Looping

--

Chapters
00:00 Bad Minute In Crontab?
00:36 Accepted Answer Score 11
00:47 Answer 2 Score 4
01:11 Answer 3 Score 2
01:34 Answer 4 Score 1
01:50 Answer 5 Score 1
02:04 Thank you

--

Full question
https://superuser.com/questions/347459/b...

--

Content licensed under CC BY-SA
https://meta.stackexchange.com/help/lice...

--

Tags
#cron #crontab #syslog

#avk47

ACCEPTED ANSWER

Score 11

Use cat -v /etc/crontab to check for unintended control characters.

ANSWER 2

Score 4

Cron tab requires at least the first and last lines of the file not to be actual cron instructions. You can put comments instead - such as those below in a file:

# START CRON JOB LIST
* * * * * /path/to/script/script1.sh
0 3 * * 0 /path/to/script/script2.sh
5 0 * * 1 /path/to/script/script3.sh
# END CRON JOB LIST

Install it like so

sudo crontab -u user /path/to/cron/file

This should work for you.

ANSWER 3

Score 1

I have same error on Ubuntu 16.04. Problem have with empty assignment to MAILTO

MAILTO=

The problem I found with the help of chkcrontab

ANSWER 4

Score 1

For anyone having issues on a Mac you can check your crontab for non-printing characters by typing

crontab -l | cat -e

sudo crontab -l | cat -e

if you have a root crontab.