similar to: log rotation not working

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 needed to logrotate a fil named qmail-queue.log from qmail-scanner. So i've edit /etc/syslog.conf and changed it to: *.info;qmail-queue.none;auth.none;mail.none;authpriv.none;cron.none /var/log/messages (...) # qmail-queue logs qmail-queue /var/spool/qscan/qmail-queue.log Also, i've edit /etc/logrotate.d/syslog and changed to /var/log/messages

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

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

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

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

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

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 Handling 1 logs rotating

> 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

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

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

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

? 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

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

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,

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.

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

centos6 in regards to /etc/logrotate.d/syslog the file is in charge of processing /var/log/cron /var/log/maillog /var/log/messages /var/log/secure /var/log/spooler If I wanted to make a specific setting just for maillog (since that file gets huge really quick) would I add 1- a new file /etc/logrotate.d/maillog with the parameters just like the other files 2- add parameters in the file it is