To understand this error, it's useful to know two rules about crontab files:
#) or begin with a valid cron job schedule expression.
When cron reads each line of your crontab, if the line is not a comment it expects it to start with a valid minute expression. If for some reason it doesn't, it will raise a
Bad Minute error.
This type of error could have many causes. Here are some troubleshooting steps to identify and fix the problem.
"/tmp/crontab.gLfS38":11: bad minute
0 0 * * * /very/long/example/command/goes/here "with several very long arguments"Bad:
0 0 * * * /very/long/example/command/goes/here "with several very long arguments"
|,||List of Minutes, e.g. 1,3,5|
|-||Range of Minutes, e.g 1-10|
|/||Minute step value, e.g. 1/5|
Tip:To verify and validate your cron expression use Crontab Guru, the free and simple cron expression editor from Cronitor.
man 5 crontab
Our software, CronitorCLI, includes the free tools we always wished we had.
Scan your system and list every cron job in seconds using
cronitor list. Run any cron job instantly using
Get Started Free