search for: missingok

...te 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 { weekly rotate 5 copytruncate compress notifempty missingok } /var/log/squid/store.log { weekly rotate 5 copytruncate compress notifempty missingok # This script asks squid to rotate its logs on its own. # Restarting 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 { weekly missingok...

...size: '100M': No such file size: '100M': No such file size: '100M': No such file And this is the logstash rotate script: #cat /etc/logrotate.d/logstash /var/log/logstash/* { daily rotate 7 copytruncate compress delaycompress missingok notifempty postrotate size 100M /bin/kill -HUP `cat /var/run/logstash.pid 2>/dev/null` 2> /dev/null || true endscript } I can't find the error there. Can I have a suggestion as to what's wrong and how to correct it? Thanks, Tim -- GPG me!!...

...ogrotate. 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         #postrotate         #        systemctl stop samba &> /dev/null         #        systemctl start samba &> /dev/null         #endscript } -- My problem is, when logrotate is executed, log is rotate but after , don't l...

...example for mariadb: > /var/log/mariadb/general.log > /var/log/mariadb/slow_query.log > /var/log/mariadb/error.log > /var/log/mariadb/mariadb.log { > create 640 mysql mysql > daily > minsize 30M > notifempty > rotate 3 > missingok > compress > sharedscripts > postrotate > # # just if mysqld is really running > if test -x /usr/bin/mysqladmin && \ > /usr/bin/mysqladmin ping &>/dev/null > then >...

...log files. From the asterisk console I kept seeing the message about re-loading logger.conf over and over and it just kept creating more and more files. I baby set many different * boxes all running the same script without this problem. Here is my cron script: /var/log/asterisk/cdr-csv/*csv { missingok rotate 12 monthly create 0640 root root } /var/log/asterisk/*log /var/log/asterisk/messages { missingok rotate 5 weekly create 0640 root root sharedscripts postrotate /usr/sbin/asterisk -rx 'logger reload' > /dev/null 2> /dev/null endscript } -- Bo...

...file has been located in the /home/vmail directory. Is there a reason it shouldn?t be located in the /var/log directory with the maillog? 2. Separate from above, if I create a new logrotate script example as follows: # dovecot SIGUSR1: Re-opens the log files. /home/vmail/dovecot-deliver.log { missingok notifempty delaycompress sharedscripts postrotate /bin/kill -USR1 `cat /var/run/dovecot/master.pid 2>/dev/null` 2> /dev/null || true endscript } I get the following error only when cron tries to run it: /etc/cron.daily/logrotate: error: stat of /home/vmail/dovecot-deliver.log...

I created some scripts to logrotate. I am having a problem. After I do it, I am sending kill -HUP to the process its not using the newly created messages file again. Could someone help me out with how I can rotate asterisk's log's without killing the process? ..o-------------------------------------------------------o. Brian Fertig NOC/Network Engineer Planet Telecom, Inc. Tampa, FL

...ieb 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 root >>         #postrotate >>         #        systemctl stop samba &> /dev/null >>         #        systemctl start samba &> /dev/null >>         #endscript >> } >> >> -- >>...

...t; /var/log/mariadb/slow_query.log >>> /var/log/mariadb/error.log >>> /var/log/mariadb/mariadb.log { >>> create 640 mysql mysql >>> daily >>> minsize 30M >>> notifempty >>> rotate 3 >>> missingok >>> compress >>> sharedscripts >>> postrotate >>> # # just if mysqld is really running >>> if test -x /usr/bin/mysqladmin && \ >>> /usr/bin/mysqladmin ping &>/dev/nu...

...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 /sbin/service httpd reload > /dev/null 2>/dev/null || true endscript } CentOS 5.4: /var/log/httpd/*log { missingok notifempty sharedscripts postrotate /bin/kill -HUP `cat /var/run/httpd.pid 2>/dev/null`...

...nfig. Are these files of any use? If not what would be the best way to suppress this? I want rotate but if I can I would like to live without managing the space issues. [root at gui logrotate.d]# cat glusterfs # Rotate client logs /var/log/glusterfs/*.log { sharedscripts weekly rotate 52 missingok compress delaycompress notifempty postrotate /usr/bin/killall -HUP glusterfs > /dev/null 2>&1 || true /usr/bin/killall -HUP glusterd > /dev/null 2>&1 || true endscript } # Rotate server logs /var/log/glusterfs/bricks/*.log { sharedscripts weekly rotate 52 m...

I know about this param, I configured it and log.smbd, log.nmbd and others are rotated, log.samba is not. ----- Original Message ----- > From: "samba" <samba at lists.samba.org> > To: "Lorenzo Milesi" <maxxer at yetopen.it>, "samba" <samba at lists.samba.org> > Sent: Thursday, May 21, 2020 7:29:04 PM > Subject: Re: [Samba] log.samba

...auth required pam_env.so readenv=1 auth required pam_env.so readenv=1 envfile=/etc/default/locale #@include common-auth auth sufficient pam_winbind.so auth sufficient pam_unix.so nullok_secure use_first_pass auth optional pam_smbpass.so migrate missingok #@include common-auth auth optional pam_gnome_keyring.so #@include common-account account sufficient pam_winbind.so account required pam_unix.so #@include common-account session required pam_limits.so #@include common-session session required...

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 28.03.23 um 10:40 schrieb Rowland Penny via samba: >> >> >> On 28/03/2023 08:40, Arnaud FLORENT via samba wrote: >>> Hello >>&gt...

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 script is going wrong, and why log files for ES are growing so incredibly big? I would think that having that logro...

...g/tinc.log That creates the file "/var/log/tinc.log" correctly and reports into it. Well, because I want to have a log file by day, I have created a logrotate file (/etc/logrotate.d/tinc) that contains the following lines: ----------------------------------------- /var/log/tinc.log { missingok rotate 7 daily create 0640 root root } ----------------------------------------- When the rotate is does, the file "tinc.log" is renamed to "tinc.log.1" and a new "tinc.log" is created but the problem is that tinc server goes on reporting in the "tinc.log.1...

Hi, We are running sernet samba, and on one particular DC (debian 7.11, samba 4.5.6), when logrotate is ready rotating, "sernet-samba-ad restart" fails with: > Shutting down SAMBA AD services : ...trying once more ... (warning). > ...trying once more ... (warning). ..... > ...trying once more ... (warning). > Error: /usr/sbin/samba still running with PID=14755 from

...e permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. This is my current logrotation conf for dovecot: /var/log/dovecot*.log { rotate 10 missingok sharedscripts postrotate doveadm log reopen endscript } And the /var/log folder has these permissions: drwxrwxr-x 12 root syslog 4.0K Mar 19 12:43 log Any clues what's wrong? Thanks Michael -- Binary Kitchen Michael Heuberger 1/33 Parrish Road Sa...

Hi there This is weird. On my latest Ubuntu server Dovecot seems to write to /var/log/dovecot.log.1 instead of a recently created /var/log/dovecot.log Here my logrotate config for Dovecot: /var/log/dovecot.log { ??????? su root syslog ??????? rotate 7 ??????? missingok ??????? copytruncate ??????? create 666 root syslog ??????? sharedscripts ??????? postrotate ??????????? doveadm log reopen ??????? endscript } Doveadm should reopen it but no, still writes to old log file. Not sure, maybe it's someone else, not dovecot, writing to the log file? And he...