similar to: ElasticSearch Logrotate not working

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

On 07/28/2016 07:40 AM, Tim Dunphy wrote: > 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 > } > >

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

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

Ok, I have Googled this and either I am not asking the right way or I just can't see what's in front of me (sorry)... We have log files called app.2011-10-119.log (with the date changing every day). The log is created by the application each day at midnight. I have logrotate set to rotate files ending in .log at 4am, with copytruncate on by default. If I list the files I see all the old

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

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

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

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

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

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:

<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

Am 28.03.23 um 10:40 schrieb Rowland Penny via samba: > > > On 28/03/2023 08:40, Arnaud FLORENT via samba wrote: >> Hello >> >> >> i am running samba 4.16 as AD-DC controller on Ubuntu 20.04 using >> www.corpit.ru/mjt/packages/samba focal/samba-4.16 repository >> >> >> everything is running fine but i have few log files in /var/log/samba/

Hi, We recently migrated the samba-ad-dc from 4.6.5 to 4.7.1. Over a period of last 15 days or so we have been observing that although the samba log rotates, upon rotation, samba will start writing the logs to both the main log file and the <main log>.old file simultaneously. While, the main log file rotates properly, instead of deleting old file and create a new one on rotation, samba

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

OK, maybe not even best practices, but at least, tested practices. >From my reading thus far, it is evident I shouldn''t use Rails to handle mongrel log rotation. Fine, I''m sold on that. The advice I''m seeing says that that one should use an external script to do this. So my question is, what are people using? What''s working well? Simple bash scripts or

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