similar to: logrotate, syslog, and chsh

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

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:

The 2.04b rpm for rh60 ships with and installs a config file for logrotate (the samba.log file in the packaging/RedHat section). ===== /var/log/samba/log.nmb { postrotate /usr/bin/killall -HUP nmbd endrotate } /var/log/samba/log.smb { postrotate /usr/bin/killall -HUP smbd endrotate } ===== 1) I think that the use of "endrotate" is wrong. There is no

Ever since a recent power failure I have been getting a Logrotate error. My machine is on a UPS -- it shutdown cleanly, but I suspect that its BIOS/RTC battery is dead, since the machine came up thinking it was 1982 :-(. I reset the clock and everything is fine, *except* I had to delete Logrotate's state files (which had bad dates). But now Logrotate is raising the error: error: error

In rhtml, you have access to controller. I am trying to set an instance var in my controller, then retrieve it in my form display. I know I could do this through one of the hashes I have access to, but I''m trying to understand why I can''t do it this way. No matter what, when I try to output from my rhtml either <%= controller.whynot || ''Unknown'' %> or

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

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

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

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 configured a specific logrotate task to rotate certain logs every hour and everytime this logrotate's task runs, I am receiving an email like this: Auto-Submitted: auto-generated Precedence: bulk X-Cron-Env: <LANG=en_US.UTF-8> X-Cron-Env: <LC_ALL=en_US.UTF-8> X-Cron-Env: <XDG_SESSION_ID=4502> X-Cron-Env: <XDG_RUNTIME_DIR=/run/user/0> X-Cron-Env:

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

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

On 01.05.2017 13:15, James Pearson wrote: > Walter.H at mathemainzel.info: >> 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 >>

Hi all, i have problem, after uprade CentOS 5.5 to 5.6, Logrotate don't work on two proxy servers. I have installed : squid-2.6.STABLE21-6.el5 logrotate-3.7.4-9.el5_5.2 On first server , squid logs never rotated, config is here cat /etc/logrotate.d/squid /var/log/squid/access.log { weekly rotate 5 copytruncate compress notifempty missingok } /var/log/squid/cache.log

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

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.