Wildcard not working in service escalations ?

[Mihai Tanasescu]

Mihai Tanasescu wrote:
> Marc Powell wrote:
>   
>>   
>>     
>>> -----Original Message-----
>>> From: Mihai Tanasescu [mailto:mihai at duras.ro]
>>> Sent: Wednesday, July 25, 2007 5:43 PM
>>> To: Marc Powell
>>> Cc: nagios-users at lists.sourceforge.net
>>> Subject: Re: [Nagios-users] Wildcard not working in service
>>>     
>>>       
>> escalations ?
>>   
>>     
>>> Marc Powell wrote:
>>>     
>>>       
>>   
>>     
>>>> I _would_ say that use_regexp_matching really isn't enabled but if
>>>>       
>>>>         
>> you
>>   
>>     
>>>> have other regexp directives that are working, that shoots that
>>>>       
>>>>         
>> down. If
>>   
>>     
>>>> someone else can duplicate it you may have discovered a bug.
>>>>       
>>>>         
>> Unusual,
>>   
>>     
>>>> but possible.
>>>>       
>>>>         
>>   
>>     
>>> Umm...sorry seems you were right (I don't know why I had the
>>>     
>>>       
>> impression
>>   
>>     
>>> that I was already using regexps somewhere in the config).
>>>
>>> I have in nagios.cfg the
>>>
>>> use_regexp_matching=1
>>>
>>> but it doesn't seem to function in any of the possible places where
>>>     
>>>       
>> the
>>   
>>     
>>> "*" character could be used.
>>>
>>> Any idea why ?
>>>     
>>>       
>> No, not really. You're looking at the right nagios.cfg, yes? Any
>> possibility that the nagios daemon is looking at another one that
>> doesn't have it enabled?
>>
>>   
>>     
>
> It's the right one unfortunately this time.
>
> nagios # ps -ax | grep nagios
> 87215  ??  Ss     1:13.47 /usr/local/bin/nagios -d 
> /usr/local/etc/nagios/nagios.cfg
> nagios # cat /usr/local/etc/nagios/nagios.cfg | grep use_regexp
> use_regexp_matching=1
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null
>   
I've solved the problem with the help of a Freenode user.

It seems that contrary to what I believed, in order for the * to match 
everything you should have:

use_regexp_matching=0

I got confused upon reading the manual and only attempted with it = 1.
(the  manual stated:
If you wish, you can enable regular expression matching for object names by using the use_regexp_matching <http://nagios.sourceforge.net/docs/2_0/configmain.html#use_regexp_matching> config option.  By default, regular expression matching will only be used in object names that contain the *** and *?* wildcard characters.)

Glad that's over with.

Maybe this will prove useful to others.




-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null