similar to: cron.daily and others, not running

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

> > 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

Hi, I just configured SquidAnalyzer, a nifty little network statistics tool that I'm using mainly in school networks to monitor network usage. I want to run the '/usr/bin/squid-analyzer' script once a day. I took a peek in /etc/cron.daily, and the package already installed an /etc/cron.daily/0squidanalyzer script. I wanted to know at what time CentOS ran the cron.daily scripts,

> > 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 It's not a service. As I said, it's run using a script in /etc/cron.hourly > > Sure, anacron is not installed. So how could stuff in /etc/cron.{daily,weekly} > work until June

Is one meant to have one or the other? If so, which is recommended? I have -------------------------------- [tim at helen etc]$ cat anacrontab # /etc/anacrontab: configuration file for anacron # See anacron(8) and anacrontab(5) for details. SHELL=/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin MAILTO=root 1 65 cron.daily run-parts /etc/cron.daily 7 70 cron.weekly

Hi all, I wanted to schedule some rsync backups and found that CentOS is by default using anacron. I'm mostly used with the historical cron, but let's follow the progress :-) - I made a shell script in /etc/cron.daily/dobackup - I made it 755, root.root. - In /etc/anacrontab, START_HOURS_RANGE=21-23 (I kept the other lines unchanged) - When I manually run /etc/cron.daily/dobackup, it

> Date: Thursday, July 20, 2017 02:25:52 +0000 > From: Richard <lists-centos at listmail.innovate.net> > >> Date: Wednesday, July 19, 2017 23:31:10 +0000 >> From: Chad Cordero <ccordero at csusb.edu> >> >> It?s being rejected before it even reaches the mailbox, so >> forwarding won?t work.? Crond should really be using the MAILTO >>

Hello, I have 2 servers which share 2 partitions with drbd, on each machine runs one VM on the drbd device, so that I have primary/secondary and secondary/primary drbd devices. There are also some more XEN VM?s that only do aa mysql replication and one is standalone. In the last 4 weeks I had 2 incidents where both machines did a sudden reboot, first one machine and 2 minutes later the other one.

It?s being rejected before it even reaches the mailbox, so forwarding won?t work.? Crond should really be using the MAILTO variable and it?s not. --- Chad Cordero Information Technology Consultant Enterprise & Cloud Services Information Technology Services California State University, San Bernardino 5500 University Pkwy San Bernardino, CA 92407-2393 Main Line: 909/537-7677 Direct

Hi all, CentOs has choosen anacron as default cron daemon. I did not look further about the reasons, I think there are some good reasons. I want to create a minute based set of scripts. No much precision required, once a minute more or less 20 sec is OK. Using anacron, how do you recommend to do it? Is anacron the right tool? Otherwise what's the right tool? -- RMA.

Hi, Up until now I always kept my servers up-to-date manually. Currently I'm experimenting with yum-cron to automate this process. I read through various online tutorials, and now I have a couple questions. 1. As far as I know, when editing /etc/yum/yum-cron.conf, I can only use the following value for update_cmd : update_cmd = default If I understand this correctly, 'update_cmd =

Well, I feel silly.? There are three places MAILTO can affect crond: /etc/crontab, /etc/crond.d/0hourly, and /etc/anacrontab.? Once I set this in these 3 files, I started getting mail from crond.? Thank you all for your help. --- Chad Cordero Information Technology Consultant Enterprise & Cloud Services Information Technology Services California State University, San Bernardino 5500

Has anyone else seen a problem recently (like, the last few weeks) with anacron? We've got a couple of recently-built systems and we're seeing Mar 4 17:20:01 <system> crond[25767]: (root) PAM ERROR (Failure setting user credentials) Mar 4 17:20:01 <system> crond[25767]: (root) FAILED to authorize user with PAM (Failure setting user credentials) mark

Am 11.05.2017 um 20:30 schrieb Larry Martell: > On Wed, May 10, 2017 at 3:19 PM, Larry Martell <larry.martell at gmail.com> wrote: >> On Wed, May 10, 2017 at 3:07 PM, Jonathan Billings <billings at negate.org> wrote: >>> On Wed, May 10, 2017 at 02:40:04PM -0400, Larry Martell wrote: >>>> I have a CentOS 7 system that I run a home grown python daemon on. I

EL6 context: cronie-1.4.4-16.el6_8.2.x86_64 cronie-anacron-1.4.4-16.el6_8.2.x86_64 crontabs-1.10-33.el6.noarch I have some cron.d entries that execute scripts in minute intervals and I'm wondering how could an "official" way look like, to have a condition to not run cron.d entries when cron.daily scripts are running. Sure, I can hack something around file timestamps or so but

On Fri, May 12, 2017 at 11:44 AM, Larry Martell <larry.martell at gmail.com> wrote: > On Thu, May 11, 2017 at 7:58 PM, Alexander Dalloz <ad+lists at uni-x.org> > wrote: > > Am 11.05.2017 um 20:30 schrieb Larry Martell: > >> > >> On Wed, May 10, 2017 at 3:19 PM, Larry Martell <larry.martell at gmail.com > > > >> wrote: > >>>

On Fri, 2019-11-15 at 16:32 -0500, Karl Vogel wrote: > > > On Fri, Nov 15, 2019 at 05:54:07PM +0000, John Horne wrote: > > J> In trying to resolve a problem with a cron job, we can see when the job > J> starts by looking in the /var/log/cron log file. However, I was asked if > J> when the job ends could also be logged. (It seems to be something that > J> crops

Hi all, I am having strange problems with my cron jobs in my CentOS7 kvm host. After the initial install and first boot, any cron job configured had run (including cron tasks installed by some rpm packages). Last cron's entry log is: Oct 9 17:01:01 santgraal CROND[9014]: (root) CMD (run-parts /etc/cron.hourly) Oct 9 17:01:01 santgraal run-parts(/etc/cron.hourly)[9014]: starting 0anacron

On Thu, July 20, 2017 8:54 am, Richard wrote: > >> Date: Thursday, July 20, 2017 02:25:52 +0000 >> From: Richard <lists-centos at listmail.innovate.net> >> >>> Date: Wednesday, July 19, 2017 23:31:10 +0000 >>> From: Chad Cordero <ccordero at csusb.edu> >>> >>> It???s being rejected before it even reaches the mailbox, so

On Mon, Jun 20, 2016 at 05:02:32PM -0400, m.roth at 5-cent.us wrote: > Fred Smith wrote: > > On Mon, Jun 20, 2016 at 04:13:35PM -0400, m.roth at 5-cent.us wrote: > >> Fred Smith wrote: > >> > On Mon, Jun 20, 2016 at 02:59:29PM -0400, Jon LaBadie wrote: > >> >> On Mon, Jun 20, 2016 at 08:58:54AM -0400, Fred Smith wrote: > >> >> > On