similar to: 2.0.4b: logrotate problems with rh60

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:

2.0.5 (on linux) has a small annoyance in that, when the log files get rotated, kill -HUP won't point the daemons to the new log files. They keeps logging to the old ones until they are stopped/started. Does 2.0.6 fix this?

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 {

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

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

I created some scripts to logrotate. I am having a problem. After I do it, I am sending kill -HUP to the process its not using the newly created messages file again. Could someone help me out with how I can rotate asterisk's log's without killing the process? ..o-------------------------------------------------------o. Brian Fertig NOC/Network Engineer Planet Telecom, Inc. Tampa, FL

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

Icecast 2.1.0 Debian 3.0 I'm trying to use logrotate to rotate my Icecast logs and I'm running into some problems because it seems that Icecast won't write to the new log after rotation takes place. I'd really rather not do a full restart of Icecast everytime I rotate the log, since I don't want to disconnect a large number of listeners. Is there a signal that can be sent to

Hello! I having a problem with the permissions of some of my logfiles. It seems that when the files are rotated, the user/group is root root and the permissions are rw for root only. more info hereunder: The strange thing is that sometimes it works for one file... /var/log/cisco_acl.log /var/log/cisco_debug.log { rotate 1 notifempty #daily size 1k create 0640 root noc

I have had a RH5.2 server running Samba up for a long time. I upgraded to Mandrake 6.0. It broke Samba, so I reinstalled using the RPM on the CD. Samba works just fine, but SWAT will not! If I try to start it manually (/usr/sbin/swat) it just hangs. In /etc/services I have a line like this: swat 901/tcp In /etc/inetd.conf I have: swat stream tcp nowait.400 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 {

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

Hi, I thought that HUPing the master smbd process (and/or the child processes) was supposed to cause the logfiles to be reopened? This does not appear to happen on our installation (2.0.4b2, Solaris 2.6). If I make a connection to a share, rename the logfile and HUP/delete the daemon (either parent or child), a new file is not created. Alternatively, how about a feature where we can signal

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

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

This may have already been addressed, and I apologize if it has, but here is my issue. I have separated the TINCD log from syslog to isolate the VPN activity. By starting with daemon with the --logfile= switch It seems to work fine except that once log rotation takes place, the daemon does not recreate the log, nor will it write to the new log even if an empty file is put into place. The only

giulioo@tiscalinet.it wrote: > SOLUTION: > for samba 2.0.x I need to use > smbstatus|tr '\205\212\215\225\227\202' '\340\350\354\362\371\351' > and all is ok :-) > > If someone can explain me this I'm still waiting :) Try adding the following patch to 2.0.4b. This should fix the problem and will be in the next release. Regards, Jeremy Allison, 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

Looking at some of the stuff in /etc/logrotate.d, I see entries like this in some of the configuration files: postrotate /sbin/service privoxy reload 2> /dev/null || true >From the commandline, that doesn't work: # /sbin/service privoxy reload 2> /dev/null || true Usage: /etc/init.d/privoxy {start|stop|restart} Changing reload to restart does work: ]# /sbin/service privoxy

I got the fail2ban from epel. There were a number of issues relating to using a log file... logwatch was looking for both fail2ban and fail2ban.log logrotate file fail2ban added looked for fail2ban.log and then reset itself to syslog fail2ban itself went to syslog, over riding its fail2ban.log. took a while, but I use /var/log/fail2ban now, that finally worked through logrotates and logwatch.