Displaying 20 results from an estimated 1000 matches similar to: "Bug#289801: Logtail should output error messages to stderr, not stdout"
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 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 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 12
3
Bug#290195: violations.d/sudo and violations.ignore.d/logcheck-sudo missing sudo log entries
Package: logcheck
Version: 1.2.32
Severity: normal
It seems when someone runs a sudo command on my system, logcheck misses
it.
The second line of /etc/logcheck/violations.d/sudo matches them, but
the /etc/logcheck/violations.ignore.d/logcheck-sudo kills them.
Furthermore, when users run commands like '$ sudo rm *' in a directory
with lots of files, we reports with lines like:
Jan 13
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 Feb 16
3
Bug#295560: logcheck: Please include filename when reporting "invalid regular expression"
Package: logcheck
Version: 1.2.34
Severity: wishlist
I have a couple of home-made logcheck ignore files, and happened to
have one unescaped (and unmatched) `(' in one of the filter
lines. Because of this, cron sent a mail with the body "grep: Invalid
regular expression" - the subject is the command in the "2 * * * *"
line in /etc/cron.d/logcheck, of course.
It would be
2004 Nov 10
1
logtail ignoring information in rotated logs
Hi gang,
While writing a script that uses logtail, I noticed that logtail assumes
nothing interesting happened between its last invocation and the
rotation, which means that exciting bits of data could be lost.
This seems a bit dodgy (correct me if I'm wrong about how it works!) so
I made a dodgy patch to logtail that checks for the existence of
$logfile.0, which on Debian seems to always be
2008 Jun 24
1
Bug#446310: setting package to logcheck-database logtail logcheck, tagging 452879, tagging 450660, tagging 450697 ...
# Automatically generated email from bts, devscripts version 2.10.30
# via tagpending
#
# logcheck (1.2.65) unstable; urgency=low
#
# * ignore.d.server/courier:
# - update rules to include port information; thanks to Antoine Pardignon
# (closes: #446310).
# - ignore couriertcpd messages; thanks to Andrew Gallagher
# (closes: #451118).
# * ignore.d.server/smbd_audit:
# -
2008 Sep 19
1
Bug#499415: setting package to logcheck-database logtail logcheck, tagging 499393, tagging 499415
# Automatically generated email from bts, devscripts version 2.10.35
# via tagpending
#
# logcheck (1.3.2) experimental; urgency=low
#
# * Apply patch from Jari Aalto for fixing package description paragraph
# ordering by importence, thanks (closes: #499415)
# * Supress cron session closed messages too, thanks to Ferenc Wagner for
# noticing (closes: #499393)
#
package logcheck-database
2008 Sep 19
1
Bug#499415: setting package to logcheck-database logtail logcheck, tagging 499415
# Automatically generated email from bts, devscripts version 2.10.35
# via tagpending
#
# logcheck (1.3.2) experimental; urgency=low
#
# * Apply patch from Jari Aalto for fixing package description paragraph
# ordering by importence, thanks (closes: #499415)
#
package logcheck-database logtail logcheck
tags 499415 + pending
2008 Jun 24
1
Bug#483214: setting package to logcheck-database logtail logcheck, tagging 487208, tagging 484546, tagging 482523 ...
# Automatically generated email from bts, devscripts version 2.10.30
# via tagpending
#
# logcheck (1.2.65) unstable; urgency=low
#
# * ignore.d.server/postfix:
# - ignore connection messages for anonymous TLS connections; thanks to
# Justin Larue (closes: #486440).
# - ignore hostname verification due to DNS name not found; thanks to
# Justin Larue (closes: #486440).
# *
2008 May 15
1
Bug#471936: setting package to logcheck-database logtail logcheck, tagging 473619, tagging 478334, tagging 472368 ...
# Automatically generated email from bts, devscripts version 2.10.27
#
# logcheck (1.2.64) unstable; urgency=low
#
# * ignore.d.server/dhcp
# - Adding dhcp rules for DNS updates by ddns_remove_a()
# (closes: #459875, #472368)
# - Added dhcp "removed reverse map" rule, which occurs on DHCPRELEASE.
# * ignore.d.server/spamd
# - deal with socket connections by e.g. evolution
2008 Aug 31
1
Bug#491694: setting package to logcheck-database logtail logcheck, tagging 491694, tagging 474239, tagging 489172 ...
# Automatically generated email from bts, devscripts version 2.10.35
# via tagpending
#
# logcheck (1.3) unstable; urgency=low
#
# * Formalise the dropping of violations.d/logcheck. Please see
# /usr/share/doc/logcheck-database/NEWS.Debian.gz for more information
# (closes: #471072).
# * Add Auto-Submitted header to outgoing mails (closes: #489172).
# * ignore.d.server/kernel:
# -
2008 Mar 05
1
Bug#445072: setting package to logcheck-database logtail logcheck, tagging 444097, tagging 445069, tagging 444096 ... ... ... ... ... ... ...
# Automatically generated email from bts, devscripts version 2.10.18.1
#
# logcheck (1.2.64) unstable; urgency=low
#
# * ignore.d.server/bind:
# - moved "[bind] query $FOO denied" rule to violations.ignore.d
# (closes: #443881).
# - added bind's "AXFR ended" rule alongside "AXFR started"
# (closes: #445046).
# - added "adding an
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
2004 Aug 31
1
Bug#269318: logcheck: /etc/logcheck/ignore.d.server (add spamassassin)
Package: logcheck
Version: 1.2.26
Severity: wishlist
Please add ignore for Spamassasin's "check" messages like:
Aug 16 19:27:54 ns spamd[23853]: checking message <20040816150710.86ADA708A8 at smtp-out.hotpop.com> for nobody:65534.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.26.20040601
Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL
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 Jun 04
2
Bug#252597: logcheck: user logchecks mails should be delivered to root
Package: logcheck
Version: 1.2.20a
Severity: important
Since logcheck changed to run as user logcheck, the error mails of the cron
daemon end up in /var/mail/logcheck where nobody reads them. Mails for
logcheck should be aliased to root like all the other mails of system
accounts.
I was searching for a long time what was wrong with my logcheck not
delivering any mails. The lock directory was
2007 Jan 15
1
Bug#406973: logtail misses lines in rotated file
Package: logtail
Version: 1.2.52
Severity: normal
Tags: patch
Hi,
When a logfile is rotated, logtail misses the lines logged between the
last logtail run and the logfile rotation.
The attached patch allows to set an alternate logfile that logtail tries
to use as the old logfile if the inode has changed.
It can be used as:
logtail -f /var/log/syslog -a /var/log/syslog.1
(Please note that this
2004 Dec 25
2
Bug#287184: logcheck overwriting ownership/permissions of /etc/logcheck/* on upgrades
Package: logcheck
Version: 1.2.32
Severity: important
In postinst logcheck "fixes" permissions of /etc/logcheck/* to 750.
In my (and others on #d-d) opinion ownership and permissions should be
preserved upon package upgrades. Logcheck must not screw with my
decision to make them world readable every time it configures.
--
Peter