Displaying 20 results from an estimated 1300 matches similar to: "Bug#312376: /etc/logcheck/logcheck.ignore is no longer read"
2004 Aug 06
6
ices2 routinely abandons one of its streams
Hi everybody,
I'm in charge of an ices2 setup that's broadcasting a local radio
station on the Net, and I'm currently under fire because one of our
streams has been down twice in two days, forcing me to restart ices2 on
each occasion. Our client is understandably unhappy about this.
OUR SETUP: I've got ices2 installed on a local machine, broadcasting to
an icecast server across
2005 Apr 07
1
Bug#303661: logcheck-database: openntpd rules
Package: logcheck-database
Version: 1.2.37
Severity: normal
Hello again,
openntpd gives messages like these failry often:
Apr 7 14:25:55 terminus ntpd[673]: peer 204.17.42.202 now invalid
Apr 7 14:26:10 terminus ntpd[673]: peer 204.17.42.202 now valid
I am not sure if this is something that an admin may find relevant but they happen fairly often and they do not offer a lot of info
for me.
2005 Jul 28
2
Bug#320274: logcheck-database: Please add pop3 to dovecot
Package: logcheck-database
Version: 1.2.40
Severity: wishlist
Hi,
Please duplicate the imap-login related lines and change them to filter
out the equivalent messages emitted by pop3-login.
regards
Andrew
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel:
2007 Sep 24
3
Bug#443886: /etc/logcheck/ignore.d.server/proftpd: [proftpd] Refused user $USER for service $FOO
Package: logcheck-database
Version: 1.2.61
Severity: wishlist
File: /etc/logcheck/ignore.d.server/proftpd
Two weeks ago, I got a rush of these:
Sep 8 12:37:07 goretex proftpd: PAM-listfile: Refused user news for service proftpd
(Apparently, fail2ban managed to miss those.)
This is triggered by pam_listfile, which is used by proftpd (and other
FTP daemons) to block users listed in
2008 Dec 27
2
Bug#509885: does not cleanly update from logtail2
Package: logtail
Version: 1.2.68
Severity: normal
Hi,
logtail does not cleanly update from logtail2:
$ sudo dpkg --install /var/cache/apt/archives/logtail_1.2.68_all.deb
(Reading database ... 26564 files and directories currently installed.)
Unpacking logtail (from .../logtail_1.2.68_all.deb) ...
dpkg: error processing /var/cache/apt/archives/logtail_1.2.68_all.deb (--install):
trying to
2008 Mar 14
5
Bug#470929: dhcp: interface names can have dash in them
Package: logcheck-database
Version: 1.2.54
Severity: normal
I recently created a bridge with the name xen-local. The DHCP server gets requests
via this bridge.
I got spammed with logcheck messages about DHCPREQUESTS and the lot because the name
of the interface in the logcheck-database does not match on names with a dash in it.
-- System Information:
Debian Release: 4.0
APT prefers stable
2004 Jul 09
1
Bug#258427: logcheck/logtail didn't detect tampering logfile
Package: logcheck
wanted to work on #195935,
but found a less than funny issue, easy to reproduce:
* remove some lines in front of your logfile
* invoke logcheck
you'll get a big email with all not matching lines from that log.
not setting that to high priority because you are getting also the
newer loglines. don't know if i find time that weekend.
wanted to document it anyways.
a++
2004 Jul 21
1
Bug#260573: logcheck: ignore.d.paranoid/cron and ignore.d.server/cron swapped
Package: logcheck
Version: 1.2.23
Severity: normal
Hello,
I have:
# /bin/cat ignore.d.server/cron
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ crontab\[[0-9]+\]: \([[:alnum:]-]+\) LIST \([[:alnum:]-]+\)$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ crontab\[[0-9]+\]: \([[:alnum:]-]+\) REPLACE \([[:alnum:]-]+\)$
and:
# /bin/cat ignore.d.paranoid/cron
^\w{3} [ :0-9]{11} [._[:alnum:]-]+
2004 Aug 31
1
Bug#269315: logcheck: /etc/logcheck/ignore.d.server (add bind9 messages)
Package: logcheck
Version: 1.2.26
Severity: wishlist
Please add following bind9 server messages to ignore: i.e from below,
everything that includex "zone.*loaded" + the other messages.
Aug 16 20:24:27 ns named[3350]: shutting down: flushing changes
Aug 16 20:24:27 ns named[3350]: stopping command channel on 127.0.0.1#953
Aug 16 20:24:27 ns named[3350]: stopping command channel on
2006 Apr 21
3
Is something wrong with ices 2.0-kh60a?
Hiya Karl (and everybody else),
I noticed today that ices 2.0-kh60a came out last January, and opted to
give it a try. Unfortunately, it just wouldn't work at all, so I had to
back down to 2.0-kh60.
What I get in my log is this:
[2006-04-21 21:16:18] DBUG om_shout/check_shout_connected Time we started stream on ice.imars.net:8000/cigr.ogg
[2006-04-21 21:16:19] EROR
2005 Jan 20
2
Bug#291395: logcheck-database: Rules dirs are setuid, they should be setgid
Package: logcheck-database
Version: 1.2.33
Severity: normal
I just installed 1.2.33, and it made my rules dirs setuid, not setgid...
- Marc
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (900, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-k7
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)
Versions of
2005 Jan 09
2
Bug#289529: logcheck: "Ghandi" should be "Gandhi" in README.how.to.interpret
Package: logcheck
Version: 1.2.32
Severity: minor
"Ghandi" should be "Gandhi" in README.how.to.interpret, assuming that
you mean the Indian freedom fighter M.K. Gandhi a.k.a. Mahatma Gandhi.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.7
Locale: LANG=C, LC_CTYPE=C
2005 Mar 06
3
Bug#298291: logcheck-database: Printer out-of-paper reported
Package: logcheck-database
Version: 1.2.34
Severity: minor
I have parallel port attached printer and kernel reports whenever
printer is out of paper:
Mar 6 12:38:50 host kernel: lp0 out of paper
However, this is not a situation that should be reported by default
(IMHO) by logcheck sending report email. Thus I propose adding
following line to ignore.d.workstation/logcheck (possibly to .server
2005 Jan 11
2
Bug#289801: Logtail should output error messages to stderr, not stdout
Package: logtail
Version: 1.2.33
Severity: normal
Hi...
Logtail should not output error messages to standard output, since this
violates the principle of least surprise.
In particular, my application was broken by the semantics of logtail changing
in version 1.2.21 (when you added switches for the default arguments to
logtail). I think this was a bad move -- you broke an interface used by
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,
2005 Feb 12
3
Bug#294950: logcheck: ignore.d.server courier imaplogin: DISCONNECTED not matching
Package: logcheck
Version: 1.2.34
Severity: normal
the ignore.d.server pattern for courier 'imaplogin: DISCONNECTED' does
not match the following line:
Feb 12 16:19:47 backup imaplogin: DISCONNECTED,
user=example at example.com, ip=[::ffff:111.111.111.111],
headers=14013, body=0, time=1
This line should be ignored like the other DISCONNECTED messages. Or am
I wrong?
-- System
2005 Apr 02
3
Bug#302744: logcheck-database: postfix rules
Package: logcheck-database
Version: 1.2.36
Severity: wishlist
Hello,
I recently blew away my old logcheck-databse and lost a number of changes that i had made to postfix entries. The default database for postfix reports the
following errors that do not seem to be important...
Apr 2 13:00:19 terminus postfix/local[29516]: 574B9B3B9F: to=<doug at localhost>, relay=local, delay=13,
2005 Jan 14
3
Bug#290511: logcheck: syslogd restart in cron.daily/sysklogd causes a log message
Package: logcheck
Version: 1.2.32
Severity: wishlist
/etc/cron.daily/sysklogd restarts syslogd at the end of the script.
This causes a daily log message, currently missed by logcheck:
Jan 14 06:55:22 pyloric syslogd 1.4.1#16: restart (remote reception).
I'm currently using this regex in ignore.server.d/local-syslogd:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ syslogd 1\.4\.1#16: restart \(remote
2005 May 19
3
Bug#309772: please add ignore lines for autossh
Package: logcheck-database
Severity: wishlist
Hi!
if autossh debug is enabled it logs to syslog, thus the messages go thru
logcheck, messages are in this form
May 19 14:02:55 sagara autossh[1909]: port set to 0, monitoring disabled
so this is the ignore line
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ autossh\[[0-9]+\]: .*$
thanks,
filippo
-------------- next part --------------
A non-text attachment
2005 Aug 08
4
Bug#322036: logcheck: [manual] typo in SYNOPSIS (TIOS => OPTIONS)
Package: logcheck
Version: 1.2.35
Severity: minor
Manual page reads:
SYNOPSIS
logcheck [TIONS]
Perhaps it was intended to read:
SYNOPSIS
logcheck [OPTIONS]
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked