I have a
CentOS 6.6 server with the following packages installed:
crontabs-1.10-33.el6.noarch cronie-1.4.4-12.el6.x86_64 cronie-anacron-1.4.4-12.el6.x86_64 kernel-2.6.32-504.3.3.el6.x86_64
Sometimes, one of the backup jobs that is scheduled to run daily simply does not run. The script is not even called according to
Interesting to mention that other jobs scheduled to run exactly at the same time run without any issues.
I can't reproduce the problem and haven't spotted any patterns on it. If I do nothing, then the job runs correctly the next day as expected.
crond simply ignores just one of the multiple jobs that are supposed to run at a particular time. This only happens sporadically.
I read in a few other places people talking about adding an empty line at the end of the
crontab file. The job that's occasionally failing to run is indeed at the last line of my
I could not find any confirmation this is a real or known bug.
# tail -2 /var/spool/cron/postgres * * * * * OTHERJOB 0 21 * * * /pg_backup.sh
This is all I have in my
Mar 31 21:00:02 SERVERNAME [cron.info] CROND: (root) CMD (OTHERJOB) Mar 31 21:00:02 SERVERNAME [cron.info] CROND: (postgres) CMD (/pg_backup.sh) Mar 31 21:01:02 SERVERNAME [cron.info] CROND: (root) CMD (OTHERJOB) Apr 1 21:00:02 SERVERNAME [cron.info] CROND: (root) CMD (OTHERJOB) Apr 1 21:01:01 SERVERNAME [cron.info] CROND: (root) CMD (OTHERJOB)
OTHERJOB always run while on
pg_backup.sh was not even executed.
I've already tried restarting
crond but this keeps happening. This is affecting multiple servers with the same version of OS, kernel and
There is a newer version of
1.4.12), however upgrading it is not an option as we're already using the latest available version for
I went through the changelog for all
cronie versions after mine (
1.4.4) and haven't seem any fix to this particular problem. Also checked all commit messages.