similar to: Slightly OT: Cron for Logrotate and Squid

Hi all, i have problem, after uprade CentOS 5.5 to 5.6, Logrotate don't work on two proxy servers. I have installed : squid-2.6.STABLE21-6.el5 logrotate-3.7.4-9.el5_5.2 On first server , squid logs never rotated, config is here cat /etc/logrotate.d/squid /var/log/squid/access.log { weekly rotate 5 copytruncate compress notifempty missingok } /var/log/squid/cache.log

Ok, I have Googled this and either I am not asking the right way or I just can't see what's in front of me (sorry)... We have log files called app.2011-10-119.log (with the date changing every day). The log is created by the application each day at midnight. I have logrotate set to rotate files ending in .log at 4am, with copytruncate on by default. If I list the files I see all the old

Am 14.05.2018 um 21:08 schrieb Reindl Harald via samba: > Am 14.05.2018 um 20:56 schrieb Carlos via samba: >> /opt/samba/var/log.samba >> >> { >>   rotate 10 >>         daily >>         compress >>         dateext >>         size 100M >>         nomail >>         missingok >>         notifempty >>         create 644 root

Hey guys, I'm trying to rotate a logstash log that can grow pretty large. 3.4GB last I saw! And that's because the logrotate script I came up with didn't work. The error I get on a syntax check is this: #logrotate -f logstash size: '100M': No such file size: '100M': No such file size: '100M': No such file size: '100M': No such file size:

Hey guys, I have this log rotation script setup in my /etc/logrotate.d folder /var/log/elasticsearch/*.log { daily rotate 100 size 50M copytruncate compress delaycompress missingok notifempty create 644 elasticsearch elasticsearch } And I notice that log files are still being generated that are upwards of 7 or 8 GBs. Can anyone point out to me where the

Hi all, I have a problem with logrotate and I don't know why. In /var/log/messages appears these errors: Apr 8 15:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 16:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 17:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 18:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8

Hi! I have one problem with my logrotate. Samba version: Samba 4 7.7 (compilated) S.O.: Ubuntu 14.04 /16.04 Samba logs file: /opt/samba/var/ Logrotate File: cat /etc/logrotate.d/samba -- /opt/samba/var/log.samba {   rotate 10         daily         compress         dateext         size 100M         nomail         missingok         notifempty         create 644 root root

On Sun, 6 Mar 2016 04:34, Tim Dunphy <bluethundr at ...> wrote: > Hey guys, > > I'm trying to rotate a logstash log that can grow pretty large. 3.4GB last > I saw! > > And that's because the logrotate script I came up with didn't work. > > The error I get on a syntax check is this: > > #logrotate -f logstash > size: '100M': No such file

Anyone having problems with logrotate and CentOS 5.4? Although I have /etc/logrotate.d/mail (contents below) to rotate my maillog file, it fails to do it automatically: /var/log/maillog { compress dateext maxage 365 rotate 60 size=+1024k missingok postrotate /etc/init.d/MailScanner restart endscript } ++++++++++++++++++++++++++++ logrotate.conf:

Hi I am using Centos 5.1 and I have a weird problem with squid logs rotation. I have the file squid as follow in /etc/logrotate.d: Recently I reduce size parameter. /var/log/squid/access.log { weekly missingok rotate 10 compress create 0660 squid squid missingok size 200M postrotate /usr/sbin/squid -k rotate endscript } /var/log/squid/cache.log { weekly

On 07/28/2016 07:40 AM, Tim Dunphy wrote: > Hey guys, > > I have this log rotation script setup in my /etc/logrotate.d folder > > /var/log/elasticsearch/*.log { > daily > rotate 100 > size 50M > copytruncate > compress > delaycompress > missingok > notifempty > create 644 elasticsearch elasticsearch > } > >

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 ^

On 28.11.23 15:23, Arnaud FLORENT via samba wrote: > Hi > > > you could try a file /etc/logrotate.d/samba-local with this content > > > /var/log/samba/log.samba-dcerpcd > /var/log/samba/log.rpcd_classic > /var/log/samba/log.rpcd_winreg > /var/log/samba/log.samba-bgqd > /var/log/samba/log.rpcd_spoolss { > ?? ?weekly > ?? ?missingok > ?? ?rotate 7

? Hi people. ? I had read dovecot logging info, they say something about using log rotation to help us rotate our log, with this setup: # dovecot SIGUSR1: Re-opens the log files. /var/log/dovecot*.log { missingok notifempty delaycompress sharedscripts postrotate /bin/kill -USR1 `cat /var/run/dovecot/master.pid 2>/dev/null` 2> /dev/null || true endscript } Well, my

Hi you could try a file /etc/logrotate.d/samba-local with this content /var/log/samba/log.samba-dcerpcd /var/log/samba/log.rpcd_classic /var/log/samba/log.rpcd_winreg /var/log/samba/log.samba-bgqd /var/log/samba/log.rpcd_spoolss { ?? ?weekly ?? ?missingok ?? ?rotate 7 ?? ?compress ?? ?delaycompress ?? ?notifempty } Le 27/11/2023 ? 10:12, Stefan G. Weichinger via samba a ?crit?: > Am

I've just updated a few CentOS 5.3 servers to 5.4. One of them were a Apache Webserver. Doing a diff/check on the new ".rpmnew" config files that are made, I saw that the logrotate command for apache was changed. In 5.3 it did a reload, but in 5.4 it does a hard kill: CentOS 5.3: /var/log/httpd/*log { missingok notifempty sharedscripts postrotate

Has anyone had any success in getting Samba to correctly restart logging to the log files with the default logrotate setup (or even a modified one) from RedHat? The default setup is to move the files to another location, create a new file for Samba to fill, then send the daemons a HUP signal. I've tried some of the options that can be used in the logrotate.d/samba file (nocreate and

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

Hi, I have recently upgraded our web proxy to CentOS 5.6. Before the upgrade, squid was running fine. Since the upgrade, sometimes, squid crashes: > [root at stargate ~]# service squid status > squid dead but pid file exists Looking at log files, I think it could be related to logrotate stuff, > -rw-r----- 1 squid squid 42713088 May 3 04:02 store.log > -rw-r----- 1 squid squid

Can you try this and adjust the path's in it. #/etc/logrotate.d/samba /var/log/samba/log.smbd { weekly missingok rotate 7 postrotate [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/smbd.pid ] || /usr/bin/smbcontrol smbd reload-config endscript compress delaycompress notifempty } /var/log/samba/log.nmbd {