similar to: Permission denied when logrotating dovecot.log

Thank you. And what user/group/file perms does your dovecot.log file have? - Michael On 19/03/17 13:43, Richard wrote: > >> Date: Sunday, March 19, 2017 13:32:57 +1300 >> From: Michael Heuberger <michael.heuberger at binarykitchen.com> >> >> Hello guys >> >> Having headaches here how to make logrotation for dovecot log files >> work. Having

Well, I tried the same but it didn't work. Setting my dovecot.log to 600 with root:root is breaking my mail system. I am then unable to receive and open emails. Had to apply an ugly hack /var/log/dovecot*.log { su syslog syslog create 666 syslog syslog rotate 10 ... } Like that anyone who wants to access/write to it, can do it and all works. That's my

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

Well, I'd rather to have dovecot log alone in one log file. My initial question is that user/group and file permissions to use?? On 19/03/17 15:40, Richard wrote: > >> Date: Sunday, March 19, 2017 15:28:35 +1300 >> From: Michael Heuberger <michael.heuberger at binarykitchen.com> >> >> On 19/03/17 15:12, Richard wrote: >>>> Date: Sunday, March 19,

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

> Date: Sunday, March 19, 2017 15:28:35 +1300 > From: Michael Heuberger <michael.heuberger at binarykitchen.com> > > On 19/03/17 15:12, Richard wrote: >> >>> Date: Sunday, March 19, 2017 14:56:01 +1300 >>> From: Michael Heuberger <michael.heuberger at binarykitchen.com> >>> >>> On 19/03/17 13:43, Richard wrote:

> Date: Sunday, March 19, 2017 14:56:01 +1300 > From: Michael Heuberger <michael.heuberger at binarykitchen.com> > > On 19/03/17 13:43, Richard wrote: >> >>> Date: Sunday, March 19, 2017 13:32:57 +1300 >>> From: Michael Heuberger <michael.heuberger at binarykitchen.com> >>> >>> Hello guys >>> >>> Having

> Date: Sunday, March 19, 2017 13:32:57 +1300 > From: Michael Heuberger <michael.heuberger at binarykitchen.com> > > Hello guys > > Having headaches here how to make logrotation for dovecot log files > work. Having permission issues: > > michael.heuberger at xxx /e/l/daily ??? sudo logrotate -fv > dovecot.daily > ? > reading config file dovecot.daily

<div xmlns="http://www.w3.org/1999/xhtml">Hi all</div><div xmlns="http://www.w3.org/1999/xhtml"> </div><div xmlns="http://www.w3.org/1999/xhtml">Cannot understand, does it a bug or just a misconfiguration. In my Dovecot there are 3 files of logging (debug, info and .log)</div><div

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:

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

> On 15 Jun 2018, at 5.17, Michael Heuberger <michael.heuberger at binarykitchen.com> wrote: > > Thanks man > > You suggesting the same as https://wiki2.dovecot.org/Logging <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

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

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

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

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

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

>From the manpage: SIGNALS Dovecot handles the following signals as described: USR1 Force dovecot to reopen all configured log files (log_path, info_log_path and debug_log_path). So, you need to add kill -s USR1 `cat /var/run/dovecot/master.pod` (or wherever your distribution puts the PID for dovecot) in your log-rotate file, to tell Dovecot to use the new log

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 {

? 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