Displaying 20 results from an estimated 1000 matches similar to: "Bug#542265: sendmail-base and logcheck-database: error when trying to install together"
2004 May 28
2
Bug#251364: logcheck: preinst has bashism, fails with dash and LANG != C
Package: logcheck
Version: 1.2.20a
Severity: serious
Tags: patch
On a system where sh points to dash and LANG=es_ES, I get this:
# apt-get -y --reinstall install logcheck
Leyendo lista de paquetes... 0%
Leyendo lista de paquetes... 0%
Leyendo lista de paquetes... 23%
Leyendo lista de paquetes... Hecho
Creando ?rbol de dependencias... 0%
Creando ?rbol de dependencias... 0%
Creando ?rbol de
2005 Dec 23
4
Bug#344553: logcheck: Fails silently to read config file
Package: logcheck
Version: 1.2.42
Severity: minor
Tags: patch
Logcheck does not report any error if the config file is not readable
or does not exists. This may easily happen, as logcheck is run as
logcheck user and while one is testing a new configuration on live
system with running configuration intact.
Following fragment may help:
# Now source the config file - before things that should
2011 Mar 09
1
Bug#617527: logcheck-database: incomplete rules for scponly-full
Package: logcheck-database
Version: 1.3.13
Severity: wishlist
Hi,
scponly-full (using 4.8-4.1) in Debian is compiled with additional support for rsync, unison and SVN.
However, the logcheck rule is based on the original version and doesn't include those commands in
the regexp.
Please add those three commands to the regexp.
Best regards,
Markus
-- System Information:
Debian Release:
2004 May 26
5
Bug#251046: logcheck: invalid mktemp -p option
Package: logcheck
Version: 1.1.1-13.1woody1
Severity: important
logcheck line 56 uses "TMPDIR=$(mktemp -d -p ..." but mktemp from
woody doesn't accept -p option
Cheers, Chris
-- System Information
Debian Release: 3.0
Kernel Version: Linux ethlife-a 2.4.26-vs1.27 #4 SMP Mit Apr 28 15:20:15 MEST 2004 i686 unknown
Versions of the packages logcheck depends on:
ii cron
2011 Mar 09
1
Bug#617530: logcheck-database: log format changed for postfix/smtpd when using XFORWARD
Package: logcheck-database
Version: 1.3.13
Severity: wishlist
Hi,
after upgrading Postfix from 2.7.1-1 to 2.8.1-1 (using testing)
parts of the log format from postfix/smtpd have changed.
This problem only seems to trigger when accepting connections
in smtpd using XFORWARD (http://www.postfix.org/XFORWARD_README.html),
for example when Amavisd-new reinjects mail to postfix.
The new log lines
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 Sep 15
2
Bug#328632: Please include README.logcheck-database.gz
Package: logcheck
Version: 1.2.41
Severity: minor
man (8) logcheck says:
For hints on how to maintain rules, see README.logcheck-database.gz,
but this file is not included in /usr/share/doc/logcheck.
micah
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel:
2005 Aug 31
3
Bug#325801: logcheck: new regex to filter imap "Moved xxx bytes of new mail" messages
Package: logcheck
Version: 1.2.41
Severity: wishlist
Hi folks, thanks for your work maintaining logcheck, it works well.
When my users read their mail using imap (usually via squirrelmail,
not sure about other clients) I get a message like this in the log:
Aug 22 21:03:32 phoenix imapd[6551]: Moved 11323 bytes of new mail to /home/winky/mail/mbox from /var/spool/mail/winky host= localhost
2005 Aug 23
5
Bug#324615: new rules for imp4
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Package: logcheck-database
Version: 1.2.41
Severity: wishlist
Tags: patch
Hi,
here is one line for the imp4 package and one (I don't have more) line
from the log file. Same as with the horde3 file: I've tested it and CC
this mail to the maintainer.
by, Martin
- --
Powered by Debian GNU / Linux
-----BEGIN PGP SIGNATURE-----
Version: GnuPG
2004 Oct 21
3
Bug#277636: logcheck-database: support for dnsmasq
Package: logcheck-database
Version: 1.2.28
Severity: wishlist
Could you add support for dnsmasq for the server profile?
This is the standard dnsmasq output.
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dnsmasq\[[[:digit:]]+\]: read /etc/hosts - [[:digit:]]+ addresses$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dnsmasq\[[[:digit:]]+\]: reading /etc/resolv.conf$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+
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 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 Jun 07
2
Bug#312376: /etc/logcheck/logcheck.ignore is no longer read
Package: logcheck
Version: 1.2.39
Severity: normal
Since I've upgraded my servers to sarge, I'm getting mail every hour for
stuff that was duly included in /etc/logcheck/logcheck.ignore. Turns
out that sarge's version no longer reads that file.
If this was a conscious decision, then there should be some warning
about this when upgrading (via debconf of NEWS.Debian). Also, the
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 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 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:
2004 Dec 20
3
Bug#286532: dnsmasq: misses message for DHCPINFORM due to 283331 fix
Package: logcheck-database
Version: 1.2.32
Severity: normal
Tags: patch
The fix for 283331 exposed a bug in the dnsmasq rules. The rule was
looking for DHCPINFO, but the actual message is DHCPINFORM. Prior to
the 283331 fix, the old rule worked, because the "[()[:alnum:]]+" part
of the rule matched the "RM" at the end of DHCPINFORM.
-- System Information:
Debian Release:
2005 Jun 14
3
Bug#313601: logcheck-database: ignore mount version messages
Package: logcheck-database
Version: 1.2.39
Severity: wishlist
These are the subject of an am-utils FAQ
<URL:http://www.am-utils.org/docs/am-utils/FAQ.txt> and would be
useful in the ignored list. Note that it's either `newer' or `older'.
Jun 14 14:32:25 albion kernel: nfs warning: mount version newer than kernel
Jun 14 14:37:54 dlsy kernel: nfs warning: mount version older
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
2005 Jul 11
3
Bug#317741: logcheck-database: fails to ignore properly some lines from 'rbldnsd'
Package: logcheck-database
Version: 1.2.40
Severity: normal
Tags: patch
There are one line that is not properly ignored. I include in the report
a better version.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (400, 'testing'), (300, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: