Displaying 20 results from an estimated 3000 matches similar to: "Bug#561995: mkdir: cannot create directory `/var/lock/logcheck': Permission denied"
2009 Jul 03
1
Bug#535562: logcheck runs at normal I/O priority, and is hard-coded to nice -n10
Package: logcheck
Version: 1.2.69
Severity: normal
logcheck is a "batchy" job, but currently runs at normal I/O priority,
and is hard-coded to run with a niceness of 10. As a result logcheck
can degrade interactive performance on machines with a lot of log
traffic, relatively slow CPU or expensive I/O.
It'd be useful if the "ionice" and "schedtool" utilities
2008 Jul 21
1
merging violations.ignore.d/logcheck-* into ignore.d.*/*
Hi guys, now that violations.d/logcheck is empty,
violations.ignore.d/logcheck-* are useless and many messages that
were previously elevated and filtered there now turn up as system
events. Thus, I went ahead and merged violations.ignore.d/logcheck-*
into ignore.d.*/* in the viol-merge branch.
http://git.debian.org/?p=logcheck/logcheck.git;a=shortlog;h=refs/heads/viol-merge
Unless I hear
2009 Sep 13
1
helping out on logcheck
Hi,
I'm quite a fan of logcheck and have been using it since setting up my
sites, and I recently saw madduck's call for help on logcheck at
debaday.[0] How can I help?
[0]
http://debaday.debian.net/2009/07/19/logcheck-brilliantly-simple-log-monitoring/
P.S. Please CC me on replies, thanks!
--
Zak B. Elep -- 1486 7957 454D E529 E4F1 F75E 5787 B1FD FA53 851D
I like the idea of 256
2009 Nov 06
2
Bug#554828: logcheck: Please include rules for amd (automount daemon from am-utils package)
Package: logcheck
Version: 1.3.3
Severity: wishlist
Tags: patch
Ali Saidi submitted rules for amd from the am-utils package to Ubuntu
at https://bugs.launchpad.net/ubuntu/+source/logcheck/+bug/91438
The provided rules are located at: http://launchpadlibrarian.net/6728953/amd
Please consider including them in the next release.
I've asked where to put them, but it should probably the
2006 Feb 22
2
Bug#353962: integrate courier file in logcheck-database
Package: courier-imap-ssl,logcheck-database
Severity: wishlist
Please move /etc/logcheck/*/courier to the courier packages and out
of logcheck-database.
-- System Information:
Debian Release: testing/unstable
APT prefers stable
APT policy: (700, 'stable'), (600, 'testing'), (98, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked
2006 Jul 08
2
building the logcheck package from SVN
apt-get install svn-buildpackage
cat <<_eof >> ~/.svn-buildpackage.conf
svn-lintian
svn-linda
svn-move
_eof
mkdir logcheck; cd logcheck
svn co svn+ssh://svn.debian.org/svn/logcheck/logcheck/trunk
cd trunk
svn-buildpackage -k<your key ID> -rfakeroot
man svn-buildpackage for more. Nice, huh?
--
.''`. martin f. krafft <madduck at debian.org>
: :' :
2009 Feb 11
1
where to submit new logcheck rules?
Hi,
I've got a few logcheck ignore.d rules that I'd like to submit, one
example is sqlgrey. /usr/share/doc/logcheck/README.maintainer talks
about shipping the rules inside the package itself, so I could file a
request with sqlgrey.
However, that doesn't work because of course I don't have all the
packages I use on my network installed on my loghost. In fact, I believe
that
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
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 Feb 11
1
Bug#352337: please tighten permissions on /etc/logcheck
Package: logcheck
Severity: wishlist
I see no reason why /etc/logcheck should have any more permissions
than 0750. Please consider removing access rights from 'other'.
-- System Information:
Debian Release: testing/unstable
APT prefers stable
APT policy: (700, 'stable'), (600, 'testing'), (98, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
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:
2007 Nov 08
1
Bug#450660: logcheck: acpid rules do not filter enough
Package: logcheck
Version: 1.2.63
Severity: minor
Tags: patch
Hi,
There was recently a modification to filter acpid stuffs.
But there are still things not filtered by logcheck.
When I unplugg, then plug back my battery, I get following notifications:
System Events
=-=-=-=-=-=-=
Nov 8 21:41:31 morpork acpid: received event "ac_adapter AC0 00000080 00000000"
Nov 8 21:41:31 morpork
2010 Feb 21
1
Bug#570792: logcheck: The report doesn't support anymore the unicode characters.
Package: logcheck
Version: 1.3.6
Severity: normal
Since logcheck 1.3.6, the report send by mail doesn't support unicode characters :
Before :
To: logcheck at executor.fruit
Subject: Executor.FRUIT 2010-02-01 20:02 ?v?nements li?s ? la s?curit?
Auto-Submitted: auto-generated
From: logcheck system account <logcheck at executor.fruit>
?v?nements li?s ? la s?curit?
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
2007 Nov 25
1
Bug#452879: Logcheck doesn't ignore smbd_audit logs
Package: Logcheck
Version: 1.2.54
Distro: Debian Etch (stable)
Kernel: 2.6.18-5-686 #1 SMP
I'm trying to force logcheck (reportlevel=server) to ignore smbd_audit logs.
smbd_audit is a vfs module of samba. It writes logs into /var/log/syslog file.
Typical log looks like this:
Oct 24 08:36:14 server4 smbd_audit: Documents|Johnson|192.168.50.19|unlink
ok|Projects/doc1.pdf
I've added the
2009 Aug 18
2
Bug#542265: sendmail-base and logcheck-database: error when trying to install together
Package: logcheck-database,sendmail-base
Version: logcheck-database/1.2.69
Version: sendmail-base/8.14.3-9
Severity: serious
User: treinen at debian.org
Usertags: edos-file-overwrite
Date: 2009-08-18
Architecture: amd64
Distribution: sid
Hi,
automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the
2006 Jul 04
1
no such user
I have rules like this on my servers:
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ proftpd\[[[:digit:]]+\]:
[._[:alnum:]-]+ \([._[:alnum:]-]+\[[[:digit:].]{7,15}\]\) (- )USER
[-_.[:alnum:]]+: no such user found from [._[:alnum:]-]+
\[[[:digit:].]{7,15}\]\ to [[:digit:].]{7,15}:21$
basically, I just don't care about logins as nonexistent users,
I get so many of those that I don't even
2009 Feb 23
1
Bug#463793: rsyslogd restarts are not ignored
On Mon, 4 Feb 2008 08:15:24 +1300, martin f krafft wrote:
> logcheck has the policy not to ignore restart messages. Thanks for
> the patch, please understand that I won't be including it.
Quote from README.logcheck-database:
"Unfortunately, we don't have the time to add and update rules for
everything, therefore the following exceptions apply:
* Debug messages
* Messages
2008 Mar 15
1
Bug#471072: logcheck-database: Moving most of violations.ignore.d to ignore.d.*
Package: logcheck-database
Version: 1.2.63
Severity: normal
Given that violations.d/logcheck has been emptied by
2394562ab4a13c4510c671f01ffc8f35e97f1cd3, shouldn't most of
violations.ignore.d be moved to one of ignore.d.*? AIUI, all of these
are currently rendered useless.
(I'll gladly lend a hand; I just want to make sure this is the right
thing to do.)
-- System Information:
Debian
2009 Apr 07
1
Bug#515156: Same bug after removal + reinstall
I ran into the same problem after somebody uninstalled logcheck and I
re-installed it.
It turned out that the ownership of /var/lock/logcheck where root:root -
sudo chown logcheck:logcheck /var/lock/logcheck solved it.
I see that there already is a check for the permissions in the postinst
which (as far as I can see) *should* have fixed the permissions and
ownership there.
When re-installing