search for: logrotator

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

Dear All, Currently i am using CentOS 4.4 Linux Logrotate is not happen without -f option I have executed the following logrotate /etc/logrotate.conf manually and Logrotate command exit without any error messages If i executed with -f option then Logrotate will happen I am not sure why this is happening. Can some one throw light on this. Regards -S.Balaji

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

Removes the delaycompress line so that every rotation is compressed. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- logrotate/ovirt-logrotate.conf | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff --git a/logrotate/ovirt-logrotate.conf b/logrotate/ovirt-logrotate.conf index 8747f59..8b89a2d 100644 --- a/logrotate/ovirt-logrotate.conf +++

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, Last year, I installed Asterisk 10.4.2 and enabled logrotate on daily basis which was working perfect. Now in couple of months back, the logrotate feature is not working at all but simply appending the logs in 'messages' file. Listing down down the configuration for logrotate below; /var/log/asterisk/messages { missingok rotate 5 daily postrotate /usr/sbin/asterisk -rx 'logger

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:

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

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

Hi list, on my Debian box there is a logrotation cron job that will gzip existing /var/log/mail.log file and create a new mail.log. It seems that after running logrotation dovecot stops logging successful POP or IMAP logins to /var/log/mail.log (nevertheless, it still works to login with POP or SMTP). This is bad because pop-before-smtp mechanisms also stop working. I have deactivated

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

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

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

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

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

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

Hello guys Having headaches here how to make logrotation for dovecot log files work. Having permission issues: michael.heuberger at xxx /e/l/daily ??? sudo logrotate -fv dovecot.daily ? reading config file dovecot.daily Handling 1 logs rotating