Description of Problem:
Under some conditions crond is executing twice in a few seconds.
This seems to be the same bug as reported in
(from feb. 1990! =;-)
The bug was probably introduced between
We have several servers running both versions, and the bug is only present on the ones with -61.
A sample from the logfiles shows
Jun 21 08:09:59 intentia CROND: (root) CMD ( /sbin/rmmod -as)
Jun 21 08:09:59 intentia CROND: (root) CMD (/usr/bin/uptime >> /var/log/uptime.log)
Jun 21 08:10:01 intentia CROND: (root) CMD ( /sbin/rmmod -as)
Jun 21 08:10:01 intentia CROND: (root) CMD (/usr/bin/uptime >> /var/log/uptime.log)
This happens from time to time, with no aparent reason - one to two times a day.
It does not seem to be related to either the cpu-load, memoy-usage or other stress of the machines.
I am experiencing this problem as well on a RedHat 7.0 system. On our system, it
seems like cron is timing it's minutes incorrectly. It often runs at HH:MM:00
and HH:MM:59. This is causing us a few problems with some oracle stuff.
Same here. Redhat 7.0, patched up to the latest.
Here is a syslog snippit:
Dec 14 05:00:59 host111 CROND: (root) CMD (run-parts /etc/cron.hourly)
Dec 14 05:00:59 host111 CROND: (root) CMD (/root/mirror.rsync
> /dev/null 2>&1)
Dec 14 05:01:00 host111 CROND: (root) CMD (run-parts /etc/cron.hourly)
Dec 14 05:01:00 host111 CROND: (root) CMD (/root/mirror.rsync
> /dev/null 2>&1)
What gives? This bug has been open for six months. Is there a reason why it
is being ignored?
I have also ran into this bug - vixie-cron-3.0.1-61, Red Hat 7.0 system.
I have upgraded to -63 (from RH7.2) and we'll se if this gets fixed.
I have this problem as well. Has there been any progress made on resolving this
Yes. The upgrade to 3.0.1-63 (from Red Hat Linux 7.2) fixes the problem.
*** This bug has been marked as a duplicate of 29868 ***