similar to: Dovecot 2.2.33.2 doveadm log reopen don't work

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

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

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 {

Hai, Check the content of : /etc/logrotate.d/named If you see postrotate /etc/init.d/smbd reload > /dev/null endscript Change that to postrotate if [ -d /run/systemd/system ]; then; systemctl -q is-active named && systemctl reload named; else; /etc/init.d/named reload ; fi'; endscript Its something like that, so who pointing.. That does not matter, because this is OS

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

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

Thanks man You suggesting the same as https://wiki2.dovecot.org/Logging says? postrotate kill -s 0 `cat /var/run/dovecot/master.pid` || kill -s USR1 `cat /var/run/dovecot/master.pid` endscript Well, I already tried that and didn't work. Hence my guess that it's something else. On 15/06/18 13:19, Stephen Satchell wrote: > From the manpage: > SIGNALS > Dovecot

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

All my 3.8 fuse clients have big dumpfiles that eventually fill up /var. -bash-4.1$ ls -lh /var/run/gl* total 1.5G -rw------- 1 root root 308K Dec 8 03:34 glusterdump.31050.dump.1512722042 -rw------- 1 root root 315K Dec 8 03:34 glusterdump.31124.dump.1512722042 -rw------- 1 root root 1.5G Dec 8 03:36 glusterdump.9314.dump.1512722042 I believe this may be part of the rotatelog config.

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

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

I believe you need a 'create' statement to set the permissions. Here 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 ???????

Hi, Your crontab should normally mail you error output. But you can also run the logrotate command manually, in verbose mode. Kind regards, Tom On 17-11-17 03:35, SH Development wrote: > 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

Hi, after the upgrade from dovecot 2.2.32 to 2.2.33 we notice that the /var/log/director/director.log was empty and the log are write in the logrotate file es. /var/log/director/director.log-20171201. Log path is dovecot is: log_path = /var/log/director/director.log Logrotate configuration is: /var/log/director/director.log { ? daily ? rotate 31 ? missingok ? notifempty ? compress ?

HI, Do you have selinux activated? Maybe the context for logrotate does not allow accessing files under /home, and the root cli is not troubled by such a limitation? Why are you storing log files under /home anyway? Note: I don't use any OS with selinux, so can't really help with fixing this an issue. Regards, Tom On 17-11-17 22:42, SH Development wrote: > So, the question is, why

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

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:

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

I have one system that went totally crazy on me. It went into an infinite loop rotating * message and 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 {

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