Hello there,
I've just noticed that scripts in /etc/cron.{daily,weekly,...} are not
launched for several weeks (I noticed a `locate` not finding a recently
added binary). Exactly, it's since June 02, and `# service cron status`
says:
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 Sat 2018-06-02 19:22:57 CEST; 4 weeks 1 days
ago
Main PID: 1379 (crond)
Tasks: 1
Memory: 5.8M
CGroup: /system.slice/crond.service
`-1379 /usr/sbin/crond -n
Jun 02 19:22:57 ladybug systemd[1]: Started Command Scheduler.
Jun 02 19:22:57 ladybug systemd[1]: Starting Command Scheduler...
Jun 02 19:22:57 ladybug crond[1379]: (CRON) INFO (RANDOM_DELAY will be scaled
with factor 73% if used.)
Jun 02 19:22:57 ladybug crond[1379]: (CRON) INFO (running with inotify support)
Jun 30 11:22:01 ladybug crond[1379]: (*system*) RELOAD (/etc/crontab)
Jun 30 20:06:01 ladybug crond[1379]: (*system*) RELOAD (/etc/crontab)
<eof>
-----------
So, service is running but what could happen that makes /etc/cron.* not
being fired?
/etc/sysconfig/crond hasn't been touched and defines an empty CRONDARGS=.
Stuff in /etc/crontab is running as expected, but it's maybe not
related anyway.
Regards,
--
wwp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.centos.org/pipermail/centos/attachments/20180702/190a22d1/attachment.sig>
> > So, service is running but what could happen that makes /etc/cron.* not > being fired?You don't say, but if this is CentOS 7, then cron.daily/weekly/monthly is run using anacron, not cron. It's configured in /etc/anacrontab and is usually run once a day by the script /etc/cron.hourly/0anacron - cron.hourly is still run by cron. If the script doesn't exist, then anacron won't run and cron.daily etc won't happen. P.
Hello Pete, On Mon, 02 Jul 2018 09:59:17 +0100 Pete Biggs <pete at biggs.org.uk> wrote:> > > > So, service is running but what could happen that makes /etc/cron.* not > > being fired? > > You don't say, but if this is CentOS 7, then cron.daily/weekly/monthly > is run using anacron, not cron.Oops, yes CentOS 7, sorry. For the record: # service anacron status Redirecting to /bin/systemctl status anacron.service Unit anacron.service could not be found. You have mail in /var/spool/mail/root Sure, anacron is not installed. So how could stuff in /etc/cron.{daily,weekly} work until June 02? Probably because it didn't need anacron at all, no? I've looked at yum history, it doesn't talk at all about anacron (but cronie-anacron) so it's not been installed and removed).> It's configured in /etc/anacrontab and is usually run once a day by the > script /etc/cron.hourly/0anacron - cron.hourly is still run by cron. > If the script doesn't exist, then anacron won't run and cron.daily etc > won't happen.There's a /etc/cron.d/0hourly here: ------------- # Run the hourly jobs SHELL=/bin/bash PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root 01 * * * * root run-parts /etc/cron.hourly ------------- I'm still not sure that talking about anacron is relevant here, and I don't know why either if you say it should be anacron in CentOS 7. Regards, -- wwp -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20180702/91801244/attachment-0001.sig>