similar to: logwatch

Hello, the last 2-3 days i have a saden problem with logwatch wich i call through a cron job. when i ran the cronjob i get this continues error for the script : ---- Use of uninitialized value in concatenation (.) or string at /etc/log.d/scripts/shared/applystddate line 43, <STDIN> line 26062. Use of uninitialized value in concatenation (.) or string at

I having a problem where Logwatch is not showing any events from the /var/log/secure log file. When I run logwatch --print --range today --service sshd --detail 10 --debug 10 the end result shows this: ... LogFiles that will be processed: [0] = secure [1] = messages Made Temp Dir: /var/cache/logwatch/logwatch.sOga48bL with tempdir export LOGWATCH_DATE_RANGE='today' export

Hello, I am using multiple files for logging activities for named daemon. The files are in /var/named/chroot/var/log/named/, for example /var/named/chroot/var/log/named/general.log. I am trying to make logwatch look into them. I have created /usr/share/logwatch/default.conf/logfiles/named.conf like this: LogFile = /var/named/chroot/var/log/named/general.log *ExpandRepeats *OnlyHost

Don't remember if I already wrote about this. But ran into it tonibhg again. Logwatch as distributed with CentOS expects yum log files in different format. As result, logwatch will not report anything. The patch is really simple (and attached). Hopefully it'll be part of 4.3 (if not sooner). The upstream is not likely to patch it, since they don't distribute yum at all.

On Mon, September 14, 2015 14:51, James B. Byrne wrote: > The Logwatch imapd service script distributed with CentOS-6 does not > generate anything when I run logwatch --service all on a cyrus-imapd > host. Is this expected behaviour? Is there a separate script for > cyrus-imapd or are their configuration options required to get the > existing script to work. > > I have found

Hello I am trying to get logwatch working on CentOS 8. System is fully updated. Usually install minimal version and then add only necessary with yum. On CentOS 7: install logwatch and get daily logwatch report on mail. On CentOS 8: install logwatch but no way to get mail. Am I doing something wrong? Or miss something? Thanks in advance Blaz

> Date: Sunday, April 09, 2017 08:36:17 -0400 > From: Robert Moskowitz <rgm at htt-consult.com> > > Logwatch is installed, and I am assuming by how empty /etc/logwatch > is that it is running from defaults, which I find in > /usr/share/logwatch/default.conf/services > > I want to customize ONE service. dovecot. > > Do I copy

The Logwatch imapd service script distributed with CentOS-6 does not generate anything when I run logwatch --service all on a cyrus-imapd host. Is this expected behaviour? Is there a separate script for cyrus-imapd or are their configuration options required to get the existing script to work. I have found an ancient (2004) logwatch service script for cyrus-imapd but I was sort of hoping that

Logwatch is installed, and I am assuming by how empty /etc/logwatch is that it is running from defaults, which I find in /usr/share/logwatch/default.conf/services I want to customize ONE service. dovecot. Do I copy /usr/share/logwatch/default.conf/services/dovecot.conf to /etc/logwatch/conf/services and edit it there, or do I have to copy ALL default.conf/services/* there and modify

On Sat, September 19, 2015 06:51, Tony Mountifield wrote: > In article > <d0000782c236fbee71045dad24a43def.squirrel at webmail.harte-lyne.ca>, James B. Byrne <byrnejb at harte-lyne.ca> wrote: >> After some experimenting I have observed that overriding settings from >> /usr/share/logwatch/default.conf/logwatch.conf in >> /etc/logwatch/conf/logwatch.conf does not

CentOS 6 (amd64) up to date with latest security / bug fixes. The logwatch reports come in plain text even though the config states HTML. <begin /etc/logwatch/conf/logwatch.conf> mailer = "/usr/sbin/sendmail -t" TmpDir = /tmp MailFrom = logwatch at example.com MailTo = admin1 admin2 admin3 Range = yesterday Detail = Medium HostName = www.example.com Print = No Output = mail

I'm trying to get usable reports out of logwatch on this new system. Looks like the reports are running in an 'unformatted' mode under Postfix/Amavisd. I found a couple of programs, postfix-logwatch and amavisd-logwatch. These sound promising. I am running Amavisd as the frontend to Postfix. Is anybody running either of these as a logwatch filter? If so, is it repetitive to run

CentOS-6.6 Can logwatch be configured to display the system uptime as part of the reporting prologue? If not then what would be the recommended way of including this information in a daily logwatch report? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne

After some experimenting I have observed that overriding settings from /usr/share/logwatch/default.conf/logwatch.conf in /etc/logwatch/conf/logwatch.conf does not produce consistent results. For example, if I replace the default detail configuration in etc/logwatch/conf/logwatch.conf with: Detail = High It does indeed change the level of detail from the default Low set in

Hello, I have a couple of CentOS 5 servers, and third running in a FC6 domU. I've configured postfix on those servers to not deliver any email to the local system, but to instead relay mail to an internal mail server. I also set up /etc/aliases to send all mail to root to me, ksandhu. I can send mail on the command line, and I get it at my email address, delivered to the internal mail

On Sunday, April 19, 2015 15:46:29 Joseph L. Casale wrote: > > Can anyone point me to where my mistake is? > > First, you are creating overrides, or site specific definitions in the > platform directory. Don't do that, the distro owns and maintains this. Put > your new code in /etc/logwatch, man 8 logwatch for explanation. > > Finally, you don't show is the script

>-----Original Message----- >From: Ama Kalu [mailto:ama.kalu@cwlgroup.net] >Sent: Wednesday, November 19, 2003 9:07 PM >To: ''Tom Eastep'' >Subject: RE: [Shorewall-users] logwatch > >Thanks Tom and Andrew, > >About 2 months ago, I setup the most current (at the time) version of >logwatch, it required a service filter for IPTABLES which I did not have

After the upgrade to CentOS 5.9, all my CentOS 5 installations report only "Unmatched Entries" in the "yum" section of their daily logwatch mails. It seems the filter script /usr/share/logwatch/scripts/services/yum got broken: --------8<--------8<--------8<--------8<--------8<--------8<--------8< [root at dns01 ~]# /usr/sbin/logwatch --print --service yum

On Mon, June 15, 2015 11:16 am, Pete Geenhuizen wrote: > Enable it in /usr/share/logwatch/default.conf/services/zz-runtime.conf Thanks a lot! Helps you to be aware that you definitely missed something important if you haven't the box rebooted during more than 45-60 days... Valeri > > Pete > > On 06/15/15 09:58, James B. Byrne wrote: >> CentOS-6.6 >> >> Can

Hi all, Last week I have migrated 5 CentoS 6.2 servers to CentOS 6.3. In all of them, I receive every day problems with logwatch: /etc/cron.daily/0logwatch: Can't exec "sendmail": No such file or directory at /usr/sbin/logwatch line 1040, <TESTFILE> line 1. Can't execute sendmail -t: No such file or directory It is really strange, because I am using default config ...