May be a bug when using wildcards in some directives in serviceescalations definition
Estagiario TI Compal
helder.rodrigues at compal.pt
Fri Feb 10 13:21:16 CET 2006
well, today I tested with the new stable 2.0 version, and the problem persists.
take a look, with this config:
define serviceescalation{
hostgroup_name pt.c.*
service_description a*
first_notification 4
last_notification 0
notification_interval 30
contact_groups pt.c.it.systems
}
with a* it accepts all services:
Checking services...
Checked 1551 services.
Checking service escalations...
Checked 1551 service escalations.
by now i will use this primitive solution.
Is there any bug tracking system to submit the bug? How developers can aknowledge this bug?
thank you a lot
helder
-----Original Message-----
From: Andreas Ericsson [mailto:ae at op5.se]
Sent: Fri 2/10/2006 11:57 AM
To: Estagiario TI Compal
Cc: nagios-devel at lists.sourceforge.net
Subject: Re: [Nagios-devel] May be a bug when using wildcards in some directives in serviceescalations definition
Estagiario TI Compal wrote:
> Im running Nagios 2.0rc1.
>
Then the first step is to try upgrading to the latest version. Nagios
2.0 was released as stable a week or two back, so you should be using
that. rc1 is at least a couple of months old.
--
Andreas Ericsson andreas.ericsson at op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
More information about the Developers
mailing list