similar to: logrotate script error

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

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

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

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

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

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 {

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

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

<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

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

Hi, I want to be certain that my apache and varnish logfiles are in strict date order when rotated. I'd like to run a sort command against them before they're compressed. I've had a look at the logrotate man page, and it looks like I can use a postrotate/endscript to do this. However, I can see any reference in the documentation for how to operate on the file. All the examples

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

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

Just a wild guess, but I and others have been having problems with samba_dlz, because of named "reload." Try to see if systemctl reload named and systemctl restart named break and fix the server respectively. (if your're not using systemd, try "serivice named reload", "service named restart instead") If you have a /etc/logrotate.d/named file containing

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

Hi everyone again. I run tinc with the following command: /usr/sbin/tincd -d1 --logfile=/var/log/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 {

Hi all, I have a problem with logrotate and I don't know why. In /var/log/messages appears these errors: Apr 8 15:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 16:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 17:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8 18:01:01 plzfnsm02 logrotate: ALERT exited abnormally with [1] Apr 8

Thanks for the quick response! I read about logrotate at voip-info.org but I didn't quite understand it. I'm no asterisk/linux expert unfortunately. First of all. What exactly does happen when I run: /usr/sbin/asterisk -rx 'logger rotate' Does it clear the file and create a new one? Can I run this manually without any interruption in the system? And what does the script do? I

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 {