similar to: rpm and /etc/cron.daily/rpm

Howdy list, Hey does anyone know what the best cron job is to call logrotate to run the squid logrotations? -Or the subscribe address for a squid or logrotate mailing list (can't seem to find anything other than the usual MARC archives). I have this in /etc/logrotate.conf # rotate log files daily, they get too big otherwise, another story. daily # keep 8 weeks worth of backlogs e.g. 60

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,

I get regularily such a mail <mail> Anacron job 'cron.daily' on .... /etc/cron.daily/logrotate: error: error running non-shared postrotate script for /var/log/clamd.clamsmtp/clamsmtpd.log of '/var/log/clamd.clamsmtp/clamsmtpd.log ' </mail> content of /etc/logrotate.d/clamsmtp /var/log/clamd.clamsmtp/clamsmtpd.log { monthly notifempty missingok

This was in root's mail on a newly-installed CentOS-5 system. To: root at beauregard.localdomain Content-Type: text/plain; charset="ANSI_X3.4-1968" Subject: Anacron job for 'beauregard.localdomain' cron.daily /etc/cron.daily/logrotate: error: sa-update:3 unknown option 'notifyempty' -- ignoring line ^

So, the question is, why can I rotate the log manually, but cron returns a permission error? Do I need to tell cron to run it as sudo or something like that? Ethon > On Nov 17, 2017, at 2:29 AM, Tom Hendrikx <tom at whyscream.net <mailto:tom at whyscream.net>> wrote: > > Hi, > > > Your crontab should normally mail you error output. But you can also run > the

--- common-post.ks | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/common-post.ks b/common-post.ks index 7f40705..13632de 100644 --- a/common-post.ks +++ b/common-post.ks @@ -139,3 +139,10 @@ EOF # Remove the default logrotate daily cron job # since we run it every 10 minutes instead. rm -f /etc/cron.daily/logrotate + +# compress all logrotated files +augtool

That doesn?t seem to work either. Where do I find logs for log rotation to see the reason it failed? Ethon > On Nov 16, 2017, at 7:53 PM, Bill Shirley <bill at KnoxvilleChristian.org <mailto:bill at KnoxvilleChristian.org>> wrote: > > I believe you need a 'create' statement to set the permissions. Here > is an example for mariadb: >

Ok, I've just had issues this morning, and went and *looked*. I can see a yum-cron running monthly, sure. Running weekly, I guess. Running daily? Why? And there is *NO* reason whatever for a "yum-hourly*. None. This is CentOS, not ubuntu-snapshot-of-the-moment. I don't know if this is from upstream or not, but it's wrong. I mean, even Redmond only pushes out patches once or

I have recently noticed that my dovecot-deliver.log is huge and wanted to start rotating it. So a couple of questions: 1. Can the dovecot-deliver.log be combined with the maillog, that gets rotated weekly? If it can be done, is it advisable? Since the inception of this particular server, the log file has been located in the /home/vmail directory. Is there a reason it shouldn?t be located in

Hi all: logrotate is broken on my stock 4.1 install. After hunting and hunting I found there is a bug filed with Redhat on the issue. logrotate fails becasue my /tmp partition is mounted noexec. I understand it is that way for security reasons. The box in question is on a dedicated hosting site and that's the way it was handed off to me, built. Some said setting TMPDIR=/var/tmp;export

Hi guys, Logrotate is checked every day by cron.daily, right? I notice in logrotate.conf by default it's weekly. If I change it into monthly (now, on 12 of Feb), when will it do the monthly rotation? a. On 12 of March or b. On 1st of March? Thanks for any insight.

> > 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 been taking a look at how RedHat (and CentOS) handles logrotate. According to the man page, logrotate is supposed to be fired by cron. But when I look at root's crontab $ sudo crontab lu root no crontab for root What exactly fires logrotate (and other scheduled events like "logwatch", which ends up in root's inbox)? === Al

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.

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

After update from CentOS 3.4 to 3.5 on 3 different boxes, I got the following message from each server ============================================ Subject: Cron <root at premiere> run-parts /etc/cron.daily > /etc/cron.daily/makewhatis.cron: > > > zcat: stdout: Broken pipe > > zcat: stdout: Broken pipe > > zcat: stdout: Broken pipe > > zcat: stdout:

For a while I've been getting this in my daily reports: /etc/cron.daily/logrotate: error: /etc/logrotate.conf:26 missing end of line It appears to originate from my CentOS server (though since client root mail goes there I can't be certain. The headers don't suggest client origin, to me). I've checked the logrotate.conf script and it looks OK to the untrained eye. It ends

This completes the read only rootfs, all needed writable directories are in the tmpfs. Signed-off-by: Joey Boggs <jboggs at redhat.com> --- common-post.ks | 12 ++++++++++++ ovirt-node-image.ks | 1 + 2 files changed, 13 insertions(+), 0 deletions(-) diff --git a/common-post.ks b/common-post.ks index 0c0a3f4..44a0270 100644 --- a/common-post.ks +++ b/common-post.ks @@ -146,3

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;

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