Your message dated Sat, 16 Aug 2025 12:38:27 +0100
with message-id
<caj3buoqdgnguqfiavpa1d2spwopjqjgzyz7kajtvb2m0tpn...@mail.gmail.com>
and subject line Re: logcheck-database: please update ignore rules for nagios
has caused the Debian Bug report #591757,
regarding nagios rules
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
591757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591757
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: logcheck-database
Version: 1.2.69
Severity: wishlist
Tags: patch
hi,
please update the ignore rules for nagios:
nagios (at least nagios3) will write two lines for each passive
service check that it resives through nsca:
.... nagios3: EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;...
.... nagios3: PASSIVE SERVICE CHECK: ...
the first one is already ignored, but the last one triggers an email
every time logcheck runs if there were any passive service check results.
at least in my enviroment that makes it unusable because in my enviroment it
is normal that i recive serveral passive service results
(it would be more alarming if they are not there actually...)
so i wrote a simple rule to ignore them (see patch)
thx
albert
-- System Information:
Debian Release: 5.0.5
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
-- no debconf information
diff --git a/logcheck/ignore.d.server/nagios b/logcheck/ignore.d.server/nagios
index 9034c53..9a57d55 100644
--- a/logcheck/ignore.d.server/nagios
+++ b/logcheck/ignore.d.server/nagios
@@ -10,6 +10,7 @@
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ nagios(2|3)?: HOST DOWNTIME ALERT: [._[:alnum:]-]+;(STARTED|STOPPED);.*$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ nagios(2|3)?: HOST EVENT HANDLER: [._[:alnum:]-]+;(UP|DOWN);(SOFT|HARD);[0-9]+;.*$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ nagios(2|3)?: EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;[._[:alnum:]-]+;[^;]+;[0-9]+;.*$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ nagios(2|3)?: PASSIVE SERVICE CHECK: [._[:alnum:]-]+;.*$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ nagios(2|3)?: EXTERNAL COMMAND: (ENABLE|DISABLE)_(HOST_|HOST_SVC_|SVC_)?NOTIFICATIONS;[._[:alnum:]-]+(;[^;]+)?$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ nagios(2|3)?: EXTERNAL COMMAND: (ADD_SVC_COMMENT|ACKNOWLEDGE_SVC_PROBLEM);[._[:alnum:]-]+;[[:alnum:]]+;[0-9]+;([[:alnum:]]+;)?.*$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ nagios(2|3)?: EXTERNAL COMMAND: SCHEDULE_HOST_DOWNTIME;[._[:alnum:]-]+;[0-9;]+;[[:alnum:]]+;.*$
--- End Message ---
--- Begin Message ---
On Sat, 1 Jun 2024 13:40:50 +0100 Richard Lewis
<[email protected]> wrote:
> On Thu, 05 Aug 2010 11:28:16 +0200 Albert Dengg <[email protected]> wrote:
> The provided file proposed the following rule:
>
> ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ nagios(2|3)?: PASSIVE SERVICE
> CHECK: [._[:alnum:]-]+;.*$
>
> Is there still nned and interest in adding this - i think it needs
> some updating in 2024, for example:
> - missing a PID,
> - unclear whether the (2|3)? is still needed? the package seems to be
> nagios4 now
> - it looks quite broad(?)
>
> so i suspect the need for this rule has passed?
A year later: closing as the suggested rule looks invalid. if there is
interest in updated rules for nagios4 in trixie, please open a new bug
--- End Message ---
