🔠Want to get alerted when your Cron doesn’t run correctly?
Go to Better Stack and start monitoring in 5 minutes.
Cause of the error
Cron expects a trailing newline character at the end of each line in the
crontab. Editors like vim and nano add this character automatically.
This error may also happen when a crontab file is generated automatically and the generator failed to insert a newline character at the end of the crontab file.
Solution
Simply add a new line at the end of the crontab file. If the problem occurs frequently, it may be caused by the text editor. Check if your editor automatically adds a newline character or change your editor entirely.
Got an article suggestion?
Let us know
Explore more
Solved: Crontab bad minute error
Cron reads every line of the crontab. If the line is not a comment or an environmental variable, cron expects a correct and valid minute expression of the cronjob. If there is an invalid minute expression (e.g. a typo), cron will throw a **Bad minute error**.
Questions
How to save cron job output to file?
Any cron job can generate output. It may be log or error messages. Regardless of the nature of the output, you may want to save this output to a file. This can be done using the `>` operator.
Questions
How to view and read cron logs on Ubuntu, Debian and CentOS?
Cron can generate logs, which are very useful in troubleshooting your cron jobs. In this quick tutorial, we will take a look at cron logs – how to find them and how to read them.
Questions
How to prevent duplicate cron jobs from running?
Sometimes you may find that duplicate cronjobs are running at the same time. This may happen when the cronjob takes longer to complete than its execution interval. Here is a simple way to prevent this from happening ever again.
Questions
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
-
Solved: Crontab bad minute error
Cron reads every line of the crontab. If the line is not a comment or an environmental variable, cron expects a correct and valid minute expression of the cronjob. If there is an invalid minute expression (e.g. a typo), cron will throw a **Bad minute error**.
Questions -
How to save cron job output to file?
Any cron job can generate output. It may be log or error messages. Regardless of the nature of the output, you may want to save this output to a file. This can be done using the `>` operator.
Questions -
How to view and read cron logs on Ubuntu, Debian and CentOS?
Cron can generate logs, which are very useful in troubleshooting your cron jobs. In this quick tutorial, we will take a look at cron logs – how to find them and how to read them.
Questions -
How to prevent duplicate cron jobs from running?
Sometimes you may find that duplicate cronjobs are running at the same time. This may happen when the cronjob takes longer to complete than its execution interval. Here is a simple way to prevent this from happening ever again.
Questions
Make your mark
Join the writer's program
Are you a developer and love writing and sharing your knowledge with the world? Join our guest writing program and get paid for writing amazing technical guides. We'll get them to the right readers that will appreciate them.
Write for usWriter of the month
Marin Bezhanov
Marin is a software engineer and architect with a broad range of experience working...
Build on top of Better Stack
Write a script, app or project on top of Better Stack and share it with the world. Make a public repository and share it with us at our email.
community@betterstack.comor submit a pull request and help us build better products for everyone.
See the full list of amazing projects on github