search for: cronning

Anything interesting in the logs? sudo journalctl -xf _SYSTEMD_UNIT=crond.service

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

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,

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 =

Package: logcheck Version: 1.2.23 Severity: normal Hello, I have: # /bin/cat ignore.d.server/cron ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ crontab\[[0-9]+\]: \([[:alnum:]-]+\) LIST \([[:alnum:]-]+\)$ ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ crontab\[[0-9]+\]: \([[:alnum:]-]+\) REPLACE \([[:alnum:]-]+\)$ and: # /bin/cat ignore.d.paranoid/cron ^\w{3} [ :0-9]{11} [._[:alnum:]-]+

I am getting /tmp/yum_save_tx.2017-12..... files in /tmp one every hour. What process is making these files ??? I have stopped PackageKit so its not running. I am running CentOS 7.4. With GNOME desktop. Thanks Jerry

I dont know if i am missleaded but it seems to me that the cron type does not accept names with a ''.'' in it ? I tried to add a cron with a name cron1-$domainename and it does not accept it. If i remove the ''.'' in the domain it work. I am using .22.3 anyone seeing the same behavior ? If yes i will fill it as a bug. -- Cordialement, Ghislain ADNET. AQUEOS.

This will sound weird but the command 'asterisk -r -x reload' fails to work when issued by Cron. But it works when I issue it from a bash session. What is not configured correctly? I need to refresh the configuration every a short amount of time. rom root@localhost.localdomain Wed Jun 15 18:42:00 2005 Date: Wed, 15 Jun 2005 18:42:00 -0400 From: root@localhost.localdomain (Cron Daemon)

Hi, environment: new Centos 6 installation out of the box. somebody has an idea what causes this error mail to be sent? ---8<--- Subject: Cron <root at fileserver1> /usr/local/asc/bin/ascservicemonitor 2>&1 >/dev/null Content-Type: text/plain; charset=UTF-8 Auto-Submitted: auto-generated X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/root> X-Cron-Env:

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

On Saturday 23 of April 2016 10:08:54 AM Kahlil Hodgson wrote: > Anything interesting in the logs? > > sudo journalctl -xf _SYSTEMD_UNIT=crond.service Don't know. [root at kohrin cron.d]# sudo journalctl -xf _SYSTEMD_UNIT=crond.service -- Logs begin at ?ro 2015-12-02 22:34:16 CET. -- kwi 22 23:11:01 vz471 crond[30534]: (*system*) RELOAD (/etc/cron.d/osticket-cron) kwi 22 23:13:01

Hi. I'm installed yum-cron and set: # by default MAILTO is unset, so crond mails the output by itself # example: MAILTO=root MAILTO="root at domain.org.ua" I see in log that yum-cron done it's job: # grep "yum" /var/log/cron Aug 11 03:08:02 venti run-parts(/etc/cron.daily)[4516]: starting 0yum.cron Aug 11 03:49:30 venti run-parts(/etc/cron.daily)[4761]: finished

How do I make sure a module is loaded before puppet requests a specific resource type. For example, node ''test'' { include cron cron { "my-test-cron": } } -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from

Hi all I have a '/etc/cron.daily/push-to-backup' script which the content is: #!/bin/bash /usr/bin/rsync [... long options line ...] echo "finished pushing to the backup" Launched manually, it's OK. Waiting for cron to execute it, In the "/var/log/cron", I see the starting time and the finish time, and I see it take about 10 minutes to make the job.

Hello, all. I have operated centos 4.x and 5.x system. for 4.x system, I auto update using yum and for 5.x system, using yum-cron. but I can't find any yum-cron package (i386) like below. # yum search yum-cron(at i686, centox 5.3) Warning: No matches found for: yum-cron No Matches found # yum search yum-cron(at x86_64, centos 5.3)

It seems to me that when you setup an environement for a cron it just recreate the crontab at each run even if the cron has not changed. Seems it does not recognize actual environement settings. I put 2 environement and i got: info: Writing cron tab for aqadmin /linux/cron=puppetdcron/environment: environment changed '''' to

For some reason I cannot fathom, cron.hourly runs twice each hour on one of my two CentOS-5.4 systems, as reported in /var/log/cron: ------------------------- Mar 16 14:01:01 helen crond[27833]: (root) CMD (run-parts /etc/cron.hourly) Mar 16 14:01:01 helen crond[27834]: (root) CMD (run-parts /etc/cron.hourly) ------------------------- On the other it just runs once, as expected.

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

I've just noticed that cron.daily, etc, do not seem to be running on my CentOS-5.4 system. The scripts in /etc/cron.d/ all run fine, but those in /etc/cron.hourly, etc, seem to be ignored. I see that according to /var/log/cron these commands are seen, eg Feb 28 18:01:01 helen crond[6680]: (root) CMD (run-parts /etc/cron.hourly) but none of the scripts in this directory seem to be touched.

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;