crond doesn't work

[rmoggia]

Hi.
I need to run a script every minute.
I have followed many guides and I have done exactly what they were told to do. But it didn't get it working.
I first set up a simple command to run every minute.
This is the command:

Code: Select all

2       *       *       *       *       echo "Hello"

After I restarted the service like this:

Code: Select all

sudo systemctl restart crond.service

if I run

Code: Select all

crontab -l

I get:

Code: Select all

2       *       *       *       *       echo "Hello"

But it does not work.

This is my Centos version:

Code: Select all

centos-release-8.2-2.2004.0.1.el8.x86_64

and it is installed runs in a VM.
Any idea?
Thanks

[aks]

Your time configuration is wrong. That's every 02 minute as in 01h02, 02h02 etc....

[tunk]

What doesn't work?
I think a cron job runs in a limited environment without a
terminal, so your echo will not output anything to a terminal.
You could try something like this:
/bin/echo "Hello" >> /path/to/some/file
Also, I think it's recommended to use systemd timers instead.

[lightman47]

Also, if you are editing /etc/crontab (as I do) try:

Code: Select all

sudo chmod 644 /etc/crontab
sudo restorecon /etc/crontab
sudo systemctl restart crond

I have to reset permissions because I use emacs for editing.

[BShT]

if there something in this world that works its name is cron

cron is not windows task scheduler, cron works, cron never fails

the problem is not cron, is the environment and your command

[TrevorH]

Also read /var/log/cron and see if it is actually running your task at 2 minutes past each hour (as you told it to). It may also tell you of problems in there like a missing home directory for the user. And you never need to restart crond to get new entries recognised, if it has a problem then it's not that.

[lightman47]

And you never need to restart crond to get new entries recognised, if it has a problem then it's not that.

Thank you. Nice to know!

[rmoggia]

if there something in this world that works its name is cron

cron is not windows task scheduler, cron works, cron never fails

the problem is not cron, is the environment and your command

You're right, I had to title the post "I can't make crond work"

[BShT]

cron is headless it will never echo at your console unless you cheat its output

and use full path of everything is a good practice (OK i´m a freeBSD paranoic)

as i said cron works, look at your command and environment