search for: sharedscript

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:

...eneral.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 > /usr/bin/mysqladmin flush-logs &g...

...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 failed: Permission denied Owner on the log...

...riadb/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 >>>...

...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` 2> /dev/null || true ends...

...this may be part of the rotatelog config. 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 { shar...

...#39;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 Sandringham Auckland 10...

...untu 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 here the versions: # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeon...

...o what's wrong > and how to correct it? Multiple errors here, first hint: "man 8 logrotate" is a good start. Second: wrong order of lines: diff -U2 [code] --- your logstash-rotate +++ corrected logstash-rotate @@ -7,6 +7,7 @@ missingok notifempty - postrotate size 100M + sharedscripts + postrotate /bin/kill -HUP `cat /var/run/logstash.pid 2>/dev/null` 2> /dev/null || true endscript [/code] In short: "postrotate" line is in wrong position, add line "sharedscripts" - Yamaban.

...e is an 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 ??????????????????????? /usr/bin/mysqladmin flush-logs ??????????????? fi ??????...

...ery.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 >> /usr/bin/...

...ferent * 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 } -- Bob Knight [-w] the work option bk@minusw.com 925-449-9163

...;) 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? > >...

...r/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 >&g...

...the file and truncating it, so some logging data might be lost. When this option is used, the create option will have no effect, as the old log file stays in place. [root at srv-rhsoft:~]$ cat /etc/logrotate.d/samba /var/log/samba/* { notifempty olddir /var/log/samba/old missingok sharedscripts copytruncate }

...gt;> 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 1...

...or dovecot:</div><div xmlns="http://www.w3.org/1999/xhtml">/var/log/dovecot.log /var/log/dovecot.info /var/log/dovecot.debug {<br />  daily<br />  rotate 14<br />  missingok<br />  notifempty<br />  compress<br />  delaycompress<br />  sharedscripts<br />  postrotate<br />    doveadm log reopen<br />    chmod 666 /var/log/dovecot.log<br />    chmod 666 /var/log/dovecot.info<br />    chmod 666 /var/log/dovecot.debug<br />  endscript<br />}<br /><br />Here is the logger process in memory:&lt...

...mmand so as to close the old files and open new ones. Cheers, -- Ex Vito /var/log/asterisk/messages /var/log/asterisk/queue_log /var/log/asterisk/event_log { weekly rotate 52 dateext compress delaycompress nocreate missingok sharedscripts postrotate /usr/sbin/asterisk -rx "logger reload" endscript } _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digi...

When logs (e.g. /var/log/maillog) are rotated (e.g. to /var/log/maillog-YYYYMDD) is there a way via systemd or whatever to assign read permission to a specific group? Right now, for example - ls -l maillog* -rw------- 1 root root 3105240 Mar 13 22:04 maillog -rw------- 1 root root 1079031 Feb 24 04:39 maillog-20190224 -rw------- 1 root root 7237640 Mar 1 12:59 maillog-20190228 -rw------- 1

On 3/13/19 11:13 PM, Alice Wonder wrote: > When logs (e.g. /var/log/maillog) are rotated (e.g. to > /var/log/maillog-YYYYMDD) is there a way via systemd or whatever to > assign read permission to a specific group? Add the following line to /etc/logrotate.d/syslog, e.g. after sharedscripts: create 640 root somegroup -- Mogens Kjaer, mk at lemo.dk http://www.lemo.dk