similar to: rhel/centos alternative to logwatch?

I just launched a new mailserver that is using dovecot. My previous mailserver used courier-mail. I am expecting better things with this new server, but I was use to some login information in logwatch that I am not seeing now. For example I would get: [IMAPd] Logout stats: ==================== User | Logouts | Downloaded | Mbox Size

Hi all, Well it took a while for me to figure it out, but apparently my logwatch no longer can be mailed locally on my computer as I believe spamassassin is eating it. I can send it out to an email address outside my server though. So spamassassin is only checking incoming I guess. My question is....how do I...or should I.... Make all local mail go straight to the boxes and skip spamasassin

Hi All, I don't know enough about when errors are *really* errors. So I google a lot to read and learn. I have a few things in my Logwatch that I want to make sure I understand 1. smartd **Unmatched Entries** Problem creating device name scan list Device /dev/sda: using '-d sat' for ATA disk behind SAT layer. Device /dev/sdb: using '-d sat' for ATA disk behind SAT layer.

Found an error or two from my logwatch report from yesterday, thought I would share this in hopes this is just first time run of the problem I noticed in the Kernel report section... Also not sure why there's an issue with automount either.... but I guess I could ask on that issue as well. I am not worried about the NAMED error, this is something that happens due to one of the services that

I've recently switched to using spamassassin via a sendmail milter, rather than using procmail to invoke it. This means that I get a number of messages appearing in my maillog, and then being reported by logwatch as unmatched entries. An example of such a messages is: Feb 27 04:33:09 quail sendmail[24780]: p1R4X46P024780[2]: URIBL blacklist\n\t* [URIs: tablettoxicspillsrx.ru]\n\t* 1.5

I updated the machine that I use for a web/email server last night to 5.9, and I have this in the logwatch report this morning: QUOTE: --------------------- Smartd Begin ------------------------ Warnings: Device: /dev/sda [SAT], WARNING: There are known problems with these drives, - 1 Time(s) **Unmatched Entries** smartd 5.42 2011-10-20 r3458 [x86_64-linux-2.6.18-348.el5] (local

Howdy all, Question for anyone. I have centos 5.x on my server. Everyday I get a logwatch sent to my mailbox. I usually check every couple weeks and this time I got a surprise... Up until may 15th, the watch started with cron begin/ cron end and then went to http begin/end.... May 16th had the selinux (which I have disabled) and dovecot listings above the http begin. Cron was absent.

On CentOS5 with the latest updates applied, the logwatch filter for postfix returns way too many lines from the log. I get an "unmatched entries" message and all messages that have gone through the system is listed. Here is an example: 8F930A8092: to=<morten at foo.bar>, orig_to=<morten at localhost>, relay=local, delay=0.19, delays=0.06/0.01/0/0.12, dsn=2.0.0,

Below is a cut and past from my log files that are sent to me. This is from the last day that proftpd worked correctly. I'm not sure why proftpd was restarted as the log states: ################### LogWatch 5.2.2 (06/23/04) #################### Processing Initiated: Sun Feb 19 09:02:02 2006 Date Range Processed: yesterday Detail Level of Output: 0 Logfiles

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, 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 searching an alternative to logwatch. After too much time spent trying to configure it. I have apache log's in different files and directories, for some reason I can not put logwatch to work. Anyone know and alternative? -- -- -- Publicidad y Servicios http://www.pas-world.com Directorio http://www.precioventa.com Tienda http://informatica.precioventa.com/es/

Hi All, I've the following in the logs and am wondering why they are there. I also keep getting emails from SAMBA log-deamon (or something like that). [2003/05/19 15:24:29, 0] passdb/pdb_smbpasswd.c:getsmbfilepwent(364) getsmbfilepwent: malformed password entry (uid not number) It's not really serious (at least to me) but it's a cause for concern. Below are the details LInux

Hello, I noticed in my logwatch file I have an error with my rndc key. I could 'play' around with it and may fix it but most likey just hose things up. I think I see the problem but not 100% sure. I think the key file has 3 different names. Here's the error: **Unmatched Entries** /etc/named.conf:23: couldn't find key 'rndckey' for use with command channel

My nightly logwatch report had a never before seen section last night, "barracuda spam firewall". I have not problem with the emails it noted as being rejected. But I've always thought of "barracuda" as a commercial product. I have neither configured nor enabled any barracuda software and "yum list '*barrac*'" comes up empty. What is this? Jon -- Jon

Hello PeopleCan anybody help me?My scenario:- One computer with:a) postfix-2.6.6-2.2.el6_1.x86_64b) mysql-5.1.66-2.el6_3.x86_64c) dovecot-2.0.9-2.el6_1.1.x86_64d) dovecot-mysql-2.0.9-2.el6_1.1.x86_64Postfix and Dovecot auth over MySQLThe Problem:- logwatch show me: Dovecot disconnects: auth failed, 1 attempts: 1 Time(s) in IDLE: 2 Time(s) no auth attempts: 6 Time(s) no reason: 6

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.

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

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

It seems there was some kind of attack against dovecot on my server (CentOS-5.5) with a hundred or so logwatch entries like: ========================================= **Unmatched Entries** dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user admin dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user webmaster