similar to: Logrotate is not happing without -f option

06.12.2023 10:01, Stefan G. Weichinger via samba: > /var/log/samba/log.rpcd_* { > log.rpcd_spoolss > log.rpcd_spoolss.1 > log.rpcd_spoolss.1.1 > log.rpcd_spoolss.1.1.1 > log.rpcd_spoolss.1.1.1.1 This seems to be a limitation/defect of logrotate itself. At first you had just log.rpcd_spoolss, and at first logrotate run it rotated it to log.rpcd_spoolss.1, - now you have 2 files

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

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

Quick logrotate question for the group. To comply with a PHB mandate, I need to keep our apache logs for a minimum of 2 years, and will be periodically required to hand over chunks of the logs from specific dates/times. While extending the timeframe of logrotate is easy, I've found that there's no elegant solution in the RH/CentOS logrotate for appending dates to the filename. I'm

I am googgling right now but am unable to find a simpler description of how to get logrotate to do what i want it to do. I have a cs 1.6 server that generates quite a bit of logs. That log generation is going to increase significantly with one of my plugins i am going to be installing(logD and the impressive plugin). I want to tell logrotate to daily rotate all the logs inside my

Howdy list, Hey does anyone know what the best cron job is to call logrotate to run the squid logrotations? -Or the subscribe address for a squid or logrotate mailing list (can't seem to find anything other than the usual MARC archives). I have this in /etc/logrotate.conf # rotate log files daily, they get too big otherwise, another story. daily # keep 8 weeks worth of backlogs e.g. 60

Hi all: logrotate is broken on my stock 4.1 install. After hunting and hunting I found there is a bug filed with Redhat on the issue. logrotate fails becasue my /tmp partition is mounted noexec. I understand it is that way for security reasons. The box in question is on a dedicated hosting site and that's the way it was handed off to me, built. Some said setting TMPDIR=/var/tmp;export

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/

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

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/ > are not handl by /etc/logrotate.d/samba > > log.samba-dcerpcd > >

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

Hi Y'all, We have nginx set up and we are having problems with logrotate. The permissions and users do not seem to be any different from other machines that are working ok however the /var/log/nginx does have a directory in there that we are using to collect some special log stuff. Could this subdirectory be interfering with the logrotate process? ta Andrew [root@ ~]# logrotate -d

I'm noticing that logrotate's default configuration for rotating /var/ log/secure and /var/log/messages partially fails if root's shell is set to /bin/tcsh (via chsh). (Running on CentOS 4.4; logrotate-3.7.1-5.RHEL4). What seems to be happening is that the logrotate.d/syslog postrotate command runs: /bin/kill -HUP `cat /var/run/syslogd.pid 2> /dev/null` 2> /dev/null

I am trying to use logrotate to rotate our web logs for our various vhosted sites to cut down on space and rotate out old logs that are not necessary to keep around personally. What Im curious to find out, is how supported extended regular expressions is within the logrotate.conf file. More specifically, will logrotate be smart enough to decipher the following:

I've been taking a look at how RedHat (and CentOS) handles logrotate. According to the man page, logrotate is supposed to be fired by cron. But when I look at root's crontab $ sudo crontab lu root no crontab for root What exactly fires logrotate (and other scheduled events like "logwatch", which ends up in root's inbox)? === Al

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.

This was in root's mail on a newly-installed CentOS-5 system. To: root at beauregard.localdomain Content-Type: text/plain; charset="ANSI_X3.4-1968" Subject: Anacron job for 'beauregard.localdomain' cron.daily /etc/cron.daily/logrotate: error: sa-update:3 unknown option 'notifyempty' -- ignoring line ^

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:

I have a problem in that at first all my log files were dated 12-31-1969 and logrotate has: # more /var/lib/logrotate.status logrotate state -- version 2 "/var/log/yum.log" 1969-12-31-20:26:1 "/var/named/data/named.run" 1969-12-31-20:26:1 "/var/log/httpd/error_log" 2015-8-27-4:43:1 "/var/log/wtmp" 1969-12-31-20:26:1 "/var/log/chrony/*.log"