Can you not check a certain hostgroup?

[Niall O Broin]

On 16 Apr 2009, at 15:10, Marc Powell wrote:

>> 2009/4/16 Andrew Bruce <abruce at hope-st.ath.cx>:
>
>>> hostgroup_name   Win_All, !WinNT_old
>>
>> You can indeed do that.  I do something similar myself to check all
>> Wintel servers, but not those in a group called 'BRONZE'.
>
> And the doc link for reference --
>
> http://nagios.sourceforge.net/docs/3_0/objecttricks.html#service

Marc answered me in similar vein recently, and I am now using it, but  
I made a rather odd discovery. This

	host_name !host17, host*

works whereas this

	host_name host*, !host17

produces this error at start:

Reading configuration data...

Error: Could not find any host matching '!host17' (config file '/etc/ 
nagios3/conf.d/MM-snmp-checks.cfg', starting on line 49)
Error: Could not expand hostgroups and/or hosts specified in service  
(config file '/etc/nagios3/conf.d/MM-snmp-checks.cfg', starting on  
line 49)

***> One or more problems was encountered while processing the config  
files...

It seems that you can't place a negative match after a wildcard.







__
Kindest regards,


Niall  O Broin
MakaluMedia Group | http://makalumedia.com | +49 6151 8724600

MakaluMedia Internet & Engineering Services GmbH | Robert-Bosch  
Strasse 7 | 64293 Darmstadt | Germany
Geschäftsführer: Matt Henderson | Sitz der Gesellschaft: Darmstadt |  
Handelsregister: Amtsgericht Darmstadt HRB 6911



------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
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