Displaying 20 results from an estimated 9000 matches similar to: "Bug#498659: logcheck-database: This should be moved to an amavisd-new bug"
2008 May 15
3
Bug#481306: logcheck-database: Request for new rule: "syslog-ng : Configuration reload"
Package: logcheck-database
Version: 1.2.63
Severity: wishlist
Hi,
Can you add rule to filter out following messages:
System Events
=-=-=-=-=-=-=
May 15 07:44:48 niko syslog-ng[21911]: Configuration reload request
received, reloading configuration;
Best regards
Andrei Emeltchenko
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'),
2006 Dec 24
0
Bug#404422: logcheck-database: postfix/lmtp messages not ignored by ignore.d.server/postfix
Package: logcheck-database
Version: 1.2.51
Severity: normal
Messages such as these are no longer being filtered by logcheck
('hostname' used to replace actual hostname; 'hostname.com' used to
replace actual domain):
Dec 23 12:02:58 hostname postfix/lmtp[5047]: 38BE4C21ED: to=<root at hostname.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=4.1, delays=2/0.16/0.05/1.8,
2007 May 07
0
Bug#422618: logcheck-database: crontab should be /usr/bin/crontab
Package: logcheck-database
Version: 1.2.54
Severity: normal
Hello,
it seems crontab reports it's whole path in syslog :
May 6 16:00:03 eckmul /usr/bin/crontab[9722]: (root) LIST (nobody)
I don't have other messages from it in my logs, so I can't comment on
the other lines in /etc/logcheck/ignore.d.server/cron , but I had to
modify the LIST one with /usr/bin/crontab
Thanks,
--
2007 Oct 29
1
Bug#448510: logcheck-database: revised pattern for spamd
Package: logcheck-database
Version: 1.2.63
Severity: normal
Tags: patch
spamassassin is now reporting Unix domain sockets in the rport field.
I'm not exactly sure what changed to cause this to happen; it started
after an upgrade whose only remotely relevant package was razor.
I think the following pattern in ignore.d.server/spamd will work
^\w{3} [ :0-9]{11} [._[:alnum:]-]+
2008 Feb 09
1
Bug#464896: logcheck-database: ignore Postfix bad address syntax errors from postfix/error
Package: logcheck-database
Version: 1.2.63
Severity: wishlist
Tags: patch
The bad address syntax bounce message was previously logged by
postfix/qmgr, but in the current version of Postfix in lenny is
(at least sometimes) logged by postfix/error instead.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1,
2007 May 25
0
Bug#425967: logcheck-database: The patterns for courier-imap-ssl do not match imap, only imap-ssl
Package: logcheck-database
Version: 1.2.54
Severity: minor
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18.2-dp0
Locale: LANG=de_DE at euro, LC_CTYPE=de_DE at euro (charmap=ISO-8859-15)
Versions of packages logcheck-database depends
2008 Sep 11
0
Bug#498659: logcheck-database: amavis filter a little too verbose?
Package: logcheck-database
Version: 1.2.68
Severity: normal
Hi,
I use postfix, amavisd-new and logcheck on a lenny server, and the mails I
receive seem a little to verbose. For example, I get in the report all mails
which are received, for example:
Sep 11 08:35:11 heracles amavis[19788]: (19788-02) Passed CLEAN, [xxx.xxx.xxx.xxx] [xxx.xxx.xxx.xxx] <user at domain> -> <user at
2008 Sep 17
2
Bug#499323: logcheck-database: Logcheck fails to ignore certain OpenVPN messages
Package: logcheck-database
Version: 1.2.54
Severity: normal
Tags: patch
Logcheck fails to ignore certain lines generated by OpenVPN; the attached patch
fixes several regular expressions:
* OpenVPN does not print the full path to ifconfig or route (at least here)
* The interface name can also contain dots and does not always start with "tun"
* The startup messages now gets suppressed
2011 Apr 26
1
Bug#624197: logcheck-database: update for amavisd-new SPAMMY log entries
Package: logcheck-database
Version: 1.3.13
Severity: normal
Tags: patch
mavisd-new uses SPAMMY since 2.4.1:
http://www.mail-archive.com/amavis-user at lists.sourceforge.net/msg05055.html
patch attached.
-- System Information:
Debian Release: 6.0.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux
2006 May 21
2
Bug#368313: logcheck-database: new postfix violations ignore rule
Package: logcheck-database
Version: 1.2.39
Severity: wishlist
Hi,
I'd like to add the following rule to /etc/logcheck/violations.ignore.d/logcheck-postfix :
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/smtpd?\[[0-9]+\]: NOQUEUE: reject: RCPT from [._[:alnum:]-]+\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\]: 554 <[._[:alnum:]-]+\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\]>:
2006 Nov 12
0
Bug#398257: logcheck-database: lots of "session opened" and "session closed" information
Package: logcheck-database
Version: 1.2.49
Severity: normal
My logcheck configuration is quite a default one, ignore level server. i found the "session opened" and "session closed" ignore
lines in ignore.d.server/logcheck. but i still get those lines in the logcheck mails:
Nov 12 17:17:01 server06 CRON[32741]: (pam_unix) session opened for user root by (uid=0)
Nov 12
2006 Aug 11
0
Bug#382440: logcheck-database: Postfix rule missing in violations.ignore.d
Package: logcheck-database
Version: 1.2.47
Severity: normal
Tags: patch
Without the following logcheck line in
/etc/logcheck/violations.ignore.d, lines such as the following are
reported:
postfix/smtp[30054]: 824E9A2C1E: to=<nooneisillegal at someplace.net>,
relay=0.0.0.0[0.0.0.0], delay=1, status=sent (250 2.6.0 Ok, id=30274-22,
from MTA: 250 Ok: queued as 15140A2D0A)
This is because
2006 Apr 18
0
Bug#363336: logcheck-database: incomplete regexp for popa3d log message
Package: logcheck-database
Version: 1.2.43a
Severity: normal
Tags: patch
Hi,
Given the following popa3d log messages:
popa3d[15636]: 0 messages (0 bytes) loaded
popa3d[15993]: 1 message (3837 bytes) loaded
popa3d[15856]: 3 messages (18116 bytes) loaded
The current logcheck ruleset does not take into account that sometimes there might be multiple message_S_ to be loaded. The following patch
2008 Apr 25
1
Bug#477932: logcheck-database: bind with views - messages not filtered
Package: logcheck-database
Version: 1.2.54
Severity: normal
Tags: patch
When views are used in bind, the logcheck filters don't catch the common
informational log messages.
Added regex bits to the filter definitions.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel:
2006 May 17
2
Bug#367781: logcheck-database: postfix/smtp read timeout (port 25) regexp wrong
Package: logcheck-database
Version: 1.2.39
Severity: normal
The rule for postfix/smtp read timeout (port 25) doesn't match the
actual log message:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/smtp\[[0-9]+\]: connect to [^[:space:]]+ \[[.0-9]+\]: read timeout \(port 25\)$
A sample log line is:
May 17 17:38:16 dp postfix/smtp[12256]: connect to smtpv1.ihs.gov[198.45.3.65]: read timeout (port
2005 Mar 22
3
Bug#300888: logcheck-database: database skip postgrey ignore pattern
Package: logcheck-database
Version: 1.2.35
Severity: minor
logcheck-database contain postgrey ignore file, but postgrey first
attempt is listed in logcheck report
$ dpkg -l postgrey
ii postgrey 1.18-1
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.29-C3EZRA
Locale: LANG=it_IT,
2007 Sep 14
2
Bug#442244: logcheck-database: should include the filters from cyrus-imapd-2.2
Package: logcheck-database
Version: 1.2.54
Severity: normal
The included filters for cyrus (/etc/logcheck/ignore.d.server/cyrus) are very minimal. The cyrus-imapd-2.2 has a more
extensive ruleset (there's a /etc/logcheck/ignore.d.server/cyrus2_2 file in that package).
Please copy over the filters from cyrus-imapd-2.2. I'm running logcheck on a loghost, which doesn't run cyrus
2006 Nov 26
0
Bug#400432: logcheck-database: slapcat Initializing BDB
Package: logcheck-database
Version: 1.2.51
Severity: wishlist
I'm backup my ldap with slapcat (from package slapd) and get a entry in
syslog. Can you add to /etc/logcheck/ignore.d.server/slpad:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ slapcat: bdb_db_init: Initializing BDB database$
-- System Information:
Debian Release: 3.1
APT prefers experimental
APT policy: (1, 'experimental')
2004 Jul 11
2
Bug#254681: logcheck-database: su from cron job not necessarily to "nobody"
Package: logcheck-database
Version: 1.2.23
Followup-For: Bug #254681
Please generalize "nobody" to "[_[:alnum:]-]+", as some cron jobs
su to other users:
Jul 11 06:51:16 tux su[10385]: + ??? root:hinfo
Jul 11 06:57:25 tux su[29801]: + ??? root:www-data
Thanks.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500,
2006 May 30
2
Bug#369603: logcheck-database: new rule for dhcpd
Package: logcheck-database
Version: 1.2.44
Severity: minor
Tags: patch
Hi,
This patch changes one rule for dhcpd. It adds support for log lines of the following format:
May 30 19:36:57 server dhcpd: DHCPACK to 10.10.10.10 (aa:bb:cc:dd:ee:ff) via eth1
Regards,
Robbert
--- /root/dhcp 2006-05-30 21:50:24.000000000 +0200
+++ dhcp 2006-05-30 23:27:06.000000000 +0200
@@ -18,7 +18,7 @@