Score:0

Cronjobs not running (Job execution of per-minute job scheduled delayed)

ml flag

The cronjobs on an AlmaLinux 9 64bit system are not running.

I added 2 simple jobs to the crontab, which run fine from the command line:

[root@sendy ~]# crontab -e

* * * * *       date > ~/cron.log 2>~/cron.log
* * * * *       env > ~/env.output

It doesn't matter if I change the schedule (every 5 mins, every hour) or if I only have 1 record in the crontab, they won't execute.

crond is running:

[root@sendy ~]# service crond status

Redirecting to /bin/systemctl status crond.service
● crond.service - Command Scheduler
     Loaded: loaded (/usr/lib/systemd/system/crond.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2023-02-21 08:12:15 UTC; 1min 22s ago
   Main PID: 110386 (crond)
     CGroup: /system.slice/crond.service
             ├─110376 /usr/sbin/crond -n
             ├─110377 /usr/sbin/crond -n
             ├─110386 /usr/sbin/crond -n
             └─110404 /usr/sbin/crond -n

Feb 21 08:12:15 sendy systemd[1]: Started Command Scheduler.
Feb 21 08:12:15 sendy crond[110386]: (CRON) STARTUP (1.5.7)
Feb 21 08:12:15 sendy crond[110386]: (CRON) INFO (Syslog will be used instead of sendmail.)
Feb 21 08:12:15 sendy crond[110386]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 8% if used.)
Feb 21 08:12:15 sendy crond[110386]: (CRON) INFO (running with inotify support)
Feb 21 08:12:15 sendy crond[110386]: (CRON) INFO (@reboot jobs will be run at computer's startup.)

There are some delayed messages in the error log

[root@sendy ~]# tail -f /var/log/cron
Feb 21 08:18:01 sendy crond[110436]: (root) INFO (Job execution of per-minute job scheduled for 08:16 delayed into subsequent minute 08:18. Skipping job run.)
Feb 21 08:19:01 sendy crond[110443]: (root) INFO (Job execution of per-minute job scheduled for 08:17 delayed into subsequent minute 08:19. Skipping job run.)
Feb 21 08:20:01 sendy crond[110449]: (root) INFO (Job execution of per-minute job scheduled for 08:18 delayed into subsequent minute 08:20. Skipping job run.)
Feb 21 08:20:01 sendy crond[110450]: (root) INFO (Job execution of per-minute job scheduled for 08:18 delayed into subsequent minute 08:20. Skipping job run.)
Feb 21 08:21:01 sendy crond[110470]: (root) INFO (Job execution of per-minute job scheduled for 08:19 delayed into subsequent minute 08:21. Skipping job run.)
Feb 21 08:21:01 sendy crond[110469]: (root) INFO (Job execution of per-minute job scheduled for 08:19 delayed into subsequent minute 08:21. Skipping job run.)
Feb 21 08:22:01 sendy crond[110479]: (root) INFO (Job execution of per-minute job scheduled for 08:20 delayed into subsequent minute 08:22. Skipping job run.)
Feb 21 08:22:01 sendy crond[110478]: (root) INFO (Job execution of per-minute job scheduled for 08:20 delayed into subsequent minute 08:22. Skipping job run.)

I have no idea why this isn't working. I also can't find anything about these delayed messages on Google and how to fix them.

Ivarvdw avatar
ml flag
@GeraldSchneider Thanks, but no. It doesn't matter how I schedule jobs, they won't run.
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.