Displaying 20 results from an estimated 2000 matches similar to: "Bug#535562: logcheck runs at normal I/O priority, and is hard-coded to nice -n10"
2009 Sep 10
1
Bug#546004: logcheck-database: logcheck kernel "Treason uncloaked" filter doesn't catch ipv6 addresses.
Package: logcheck-database
Version: 1.2.69
Severity: normal
Tags: patch
kernel log lines of the form:
...kernel: [1933150.816604] TCP: Treason uncloaked!
Peer 0000:0000:0000:0000:0000:ffff:d04e:3f6b:4038/80 shrinks window
2491430013:2491430014. Repaired.
are not caught by the current rules.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500,
2009 Sep 15
0
Bug#546771: logcheck fails to locate lockfile-progs at non standart location
Package: logcheck
Version: 1.2.69
Severity: normal
Tags: patch
-- System Information:
Debian Release: 5.0.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30.4-vs2.3.0.36.14-pre4 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages logcheck depends
2010 Feb 17
1
Bug#570207: logcheck wu-ftpd rules do'nt match
Package: logcheck
Version: 1.2.69
Severity: normal
In the file /etc/logcheck/ignore.d.server/wu-ftpd
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ wu-ftpd: PAM-listfile: Refused user [._[:alnum:]-]+ for service wu-ftpd$
should be
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ wu-ftpd\[[0-9]{4}\]: PAM-listfile: Refused user [._[:alnum:]-]+ for service wu-ftpd$
There is a number after "wu-ftpd"
-- System
2010 Feb 07
2
Bug#568815: Redundant messages from dhcpd in logcheck output in "server" mode.
Package: logcheck
Version: 1.2.69
Severity: normal
Tags: patch
Logcheck's reports contains many messages like:
Feb 7 19:03:57 srv dhcpd: DHCPREQUEST for 172.21.0.126 from 00:19:7e:9f:cc:32 (Hostname
Unsuitable for Printing) via eth0
Feb 7 19:03:57 srv dhcpd: DHCPACK on 172.21.0.126 to 00:19:7e:9f:cc:32 (Hostname
Unsuitable for Printing) via eth0
I create file
2007 Jun 26
0
Bug#429384: logcheck: Logcheck depends on mktemp
Package: logcheck
Version: 1.2.56
Followup-For: Bug #429384
I get the following message in my e-mail from cron: Cron <logcheck at entercom>
if [ -x /usr/sbin/logcheck ]; then nice -n10 /usr/sbin/logcheck; fi
/usr/sbin/logcheck: line 645: mktemp: command not found
/usr/sbin/logcheck: line 646: mktemp: command not found
rm: too few arguments
Try `rm --help' for more information.
2005 Mar 16
1
Bug#299810: logcheck: grep errors after latest update
Package: logcheck
Version: 1.2.35
Severity: normal
I'm getting the following on two different Unstable boxen:
------------------------------------------------------------------------------
Subject: Cron <logcheck at bandit-hall> if [ -x /usr/sbin/logcheck ]; then
nice -n10 /usr/sbin/logcheck; fi
2006 Oct 06
0
Bug#391458: logcheck: Please provide a way to configure niceness of log scanning process
Package: logcheck
Version: 1.2.47
Severity: wishlist
I'm running logcheck with an extended set of regular expressions on a
desktop system. The CPU load of this system is normally very low, around
3%-5%. When logcheck starts scanning the logs, the CPU usage increases
to 100% for several minutes and working on the system becomes difficult.
I would therefore be very happy about if a
2010 Nov 05
0
Bug#602494: logcheck runs filters for packages not installed
Package: logcheck
Version: 1.3.13
Severity: normal
Hi, at present my logcheck is into 33 minutes of cpu time for
running the ignore/innd rule, when the innd package is not installed.
If running logcheck against only locally created logfiles, there should
be a configuration option to only run logcheck against installed (or
non-purged) packages.
-- System Information:
Debian Release: squeeze/sid
2008 Apr 06
1
Bug#474606: logcheck: add a filter for r300 microcode
Package: logcheck
Version: 1.2.63
Severity: normal
Hi,
I have just installed logcheck and it works out of the box! thx for
that!
I just notice that in the /etc/logcheck/ignore.d.workstation/kernel
file there is a filter for "[drm] Loading r200 Microcode". COuld you
add please the same for the r300. The log message is the same :
Apr 6 19:21:14 debian kernel: [drm] Loading R300
Bug#551340: [logcheck-database] Rule in /etc/logcheck/violations.ignore.d/logcheck-su does not match
2009 Oct 17
1
Bug#551340: [logcheck-database] Rule in /etc/logcheck/violations.ignore.d/logcheck-su does not match
Package: logcheck-database
Version: 1.2.69
Severity: normal
Tags: patch
Hi,
I think that this rule:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ su\[[0-9]+\]: (\+|-)
(pts/[0-9]{1,2}|tty[0-9]) [_[:alnum:]-]+:[_[:alnum:]-]+$
is supposed to filter out lines like:
Oct 17 14:49:24 myhost su[13469]: + /dev/pts/1 user1:root
It is not working because the pattern dos not include the "/dev/" part
and
2009 Dec 21
2
Bug#561995: mkdir: cannot create directory `/var/lock/logcheck': Permission denied
Package: logcheck
Version: 1.3.4
Severity: normal
I am running debian/testing and just upgraded to logcheck 1.3.4 and it
started reporting the error:
mkdir: cannot create directory `/var/lock/logcheck': Permission denied
I created the directory and chown'd it to logcheck and it seems fine now.
Looking at the changelog, I see something was purposefully changed, so I
imagine I
2010 Feb 09
1
Bug#569014: logcheck kernel rules don't match [<blank><number>.<number>]
Package: logcheck
Version: 1.2.69
The current ruleset "kernel" provided with this logcheck package don't
match entries where the kernel timeline has leading spaces, like:
[ 42.302707]
For example, the following entry:
Feb 4 17:05:24 hostname kernel: [ 144.591487] tun: Universal TUN/TAP
device driver, 1.6
didn't matched the re:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+
2009 May 04
1
Bug#526911: logcheck: Please set rsyslog as default system log daemon
Package: logcheck
Version: 1.2.69
Severity: wishlist
User: biebl at debian.org
Usertags: goal-rsyslog
Hi,
since lenny, the default syslog daemon is rsyslog. Please update
logcheck to depend on
rsyslog | system-log-daemon
so the correct default syslog daemon is installed.
(btw, the optional | syslog-ng dependency is not required, as syslog-ng
does provide system-log-daemon)
Cheers,
Michael
--
2010 Jan 11
1
Bug#564693: logcheck: should suggest/recommend nail
Package: logcheck
Version: 1.3.5
Severity: minor
Hi,
reading logcheck source it seems that it requires nail for MAILATTACH to work,
however it is not suggested/recommended.
(JFTR it is debatable if nail is appropriate or something else should be used)
thanks,
filippo
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500,
2010 Jul 22
1
Bug#589981: logcheck-database: add sender delay rules for bounce
Package: logcheck-database
Version: 1.2.69
Severity: wishlist
Please add the rule
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ postfix/bounce\[[[:digit:]]+\]: [:alnum:]+: sender delay notification: [:alnum:]+$
-- System Information:
Debian Release: 5.0.5
APT prefers stable
APT policy: (700, 'stable'), (650, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP
2010 Dec 29
1
Bug#608256: /etc/logcheck/ignore.d.server/dnsmasq: dnsmasq: interface names are allowed to have a dash (-) please add this to the filter
Package: logcheck-database
Version: 1.2.69
Severity: normal
File: /etc/logcheck/ignore.d.server/dnsmasq
A dnsmasq log about DHCP events has the interface name in it. Interface names are allowed to have a dash (-) in them,
but the logcheck filter does not have the dash in it.
Please add the dash.
-- System Information:
Debian Release: 5.0.7
APT prefers stable
APT policy: (500,
2005 Apr 28
1
Bug#306695: nagios: logcheck lines, please
On Wed, 2005-04-27 at 22:10 -0400, Steve Gran wrote:
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ nagios: EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT
>
> (although that may be too broad)
Can you provide the log messages that this matches?
Thanks,
--
-jamie <jamie at silverdream.org> | spamtrap: spam at silverdream.org
w: http://www.silverdream.org | p: sms at silverdream.org
pgp
2009 Jun 10
1
Bug#532719: logcheck-database: filter pam_env complaining about missing /etc/default/locale
Package: logcheck-database
Version: 1.2.69
Severity: normal
on systems without configured global locale, i get lines like this in
the logcheck filtered logs:
Jun 10 21:12:13 ... sshd[9729]: pam_env(sshd:setcred): Unable to open env file: /etc/default/locale: No such file or directory
this looks like a warning that is perfectly ok but does not do any harm
and occurs because when no global locale
2009 Dec 21
0
logcheck 1.3.4 MIGRATED to testing
FYI: The status of the logcheck source package
in Debian's testing distribution has changed.
Previous version: 1.2.69
Current version: 1.3.4
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.
2009 Sep 06
1
Bug#545318: logcheck-database: please add rule for newgrp messages
Package: logcheck-database
Version: 1.2.69
Severity: wishlist
Hello,
when newgrp (part of the package login) is used, I see messages
like this in my syslog:
Aug 27 23:36:16 debian64 newgrp[1975]: user `root' (login `root' on tty1)
switched to group `backup'
Aug 27 19:28:15 srv1 newgrp[10082]: user `root' (login `mazur' on pts/1)
switched to group `backup'
Aug 27