Re: [Nagios-users] low-cost snmp-enabled temperature sensor?

2010-12-10 Thread Duncan Berriman
I'd recommend 

http://www.omega.co.uk/ppt/pptsc.asp?ref=ithx-w_ithx-m

Fabulous product, plug it in and it works, used them for years.

Regards
Duncan

-Original Message-
From: Furnish, Trever G [mailto:tgfurn...@herffjones.com] 
Sent: 09 December 2010 18:17
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] low-cost snmp-enabled temperature sensor?

Can anyone recommend a low-cost external temperature sensor that doesn't
require the buyer to break out a soldering iron?

Preferably it would be SNMP-enabled so I can poll it from anything.
Power-over-ethernet would be great too.

The least expensive snmp-enabled sensor I've found so far is this one at
195 USD:
http://avtech.com/Products/Temperature_Monitors/TemPageR_3E.htm

I've also noted probes like this one at 15 USD:
http://www.ibuttonlink.com/t-sense.aspx

...but the systems in the site where I'd hook this up are all Windows, so
I'm not sure how I'd get from there into Nagios.

--
Trever Furnish, tgfurn...@herffjones.com Herff Jones, Inc. Solutions
Architect
Phone: 317.612.3519
Any sufficiently advanced technology is indistinguishable from Unix.



--
___
Nagios-users mailing list
Nagios-users@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

--
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.


--
___
Nagios-users mailing list
Nagios-users@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


Re: [Nagios-users] Check RAID Script

2010-12-09 Thread Duncan Berriman
Can't help there as never had that sort of config.

I guess you can use hpacucli to query the shelf so it should just be a
matter of adapting the script to suit (there may already be an option in the
script).

On a simple raid controller direct to disks you get something like following
as a response.

RAID OK: Smart Array 5i in Slot 0 array A logicaldrive 1 (33.9 GB, RAID 1+0,
OK) array B logicaldrive 2 (16.9 GB, RAID 1+0, OK) array C logicaldrive 3
(67.8 GB, RAID 1+0, OK)

Duncan

-Original Message-
From: Sebastian Ries [mailto:sebastian.r...@dtnet.de] 
Sent: 09 December 2010 10:11
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Check RAID Script

Hi

Am Donnerstag, den 09.12.2010, 09:43 + schrieb Duncan Berriman:
> Use check_cciss (uses hpacucli which must be installed), raid checker 
> for HP.

Thanks, I was also looking for something like this, but:

maintain:/usr/lib/nagios/plugins# ./check_cciss -v RAID OK:  [Controller
Status: OK Cache Status: OK Battery Status: OK Controller Status: OK Cache
Status: Not Configured Battery Status: OK] maintain:/usr/lib/nagios/plugins#
hpacucli controller all show

MSA20 at E0ARMLJ191   (sn: PAAACADMQUUNF7, csn: E0ARMLJ191)
Smart Array 6400  (sn: P57820R9SS32WO)

As the MSA20 is connected to the P6400 this one does not have disks directly
connected.

So is it guaranteed that both controllers are checked?
How can I configure which to check?

Regards
Sebastian Ries

--

DT Netsolution GmbH -  Talaeckerstr. 30 -  D-70437 Stuttgart
Tel: +49-711-849910-36   Fax: +49-711-849910-936
WEB: http://www.dtnet.de/ email: sebastian.r...@dtnet.de


--
This SF Dev2Dev email is sponsored by:

WikiLeaks The End of the Free Internet
http://p.sf.net/sfu/therealnews-com
___
Nagios-users mailing list
Nagios-users@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

--
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.


--
This SF Dev2Dev email is sponsored by:

WikiLeaks The End of the Free Internet
http://p.sf.net/sfu/therealnews-com
___
Nagios-users mailing list
Nagios-users@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


Re: [Nagios-users] Check RAID Script

2010-12-09 Thread Duncan Berriman
Use check_cciss (uses hpacucli which must be installed), raid checker for
HP.

 

Duncan

From: Kaushal Shriyan [mailto:kaushalshri...@gmail.com] 
Sent: 09 December 2010 09:04
To: nagios Mailinglist
Subject: [Nagios-users] Check RAID Script

 

Hi 

I have the below Raid Controller Card on HP DL 360 G6 Server. Can someone
please suggest/guide and let me know if there is a Raid Check script for
this specific model

03:00.0 RAID bus controller: Hewlett-Packard Company Smart Array G6
controllers (rev 01)
Subsystem: Hewlett-Packard Company Device 3245
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: cciss
Kernel modules: cciss

Thanks

Kaushal

-- 
This message has been scanned for viruses and 
dangerous content by   MailScanner, and is 
believed to be clean. 

--
This SF Dev2Dev email is sponsored by:

WikiLeaks The End of the Free Internet
http://p.sf.net/sfu/therealnews-com___
Nagios-users mailing list
Nagios-users@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

Re: [Nagios-users] different notification_intervals by contact

2010-11-10 Thread Duncan Berriman
Escalations are a little pesky to get working correctly.

 

Here is an example.

 

define serviceescalation{

host_name   .*

service_description .*

first_notification  1

last_notification   0

notification_interval   60

contact_groups  admins

escalation_period   24x7

escalation_options  w,u,c,r

}

 

define serviceescalation{

host_name   .*

servicegroup_name
disks,dns,firewall,load,mailq,processes,sendmail,ssh,time

first_notification  2

last_notification   2

notification_interval   60

contact_groups  support

escalation_period   24x7

escalation_options  w,u,c,r

}

 

define hostescalation{

host_name   .*

first_notification  1

last_notification   0

notification_interval   60

contact_groups  admins

escalation_period   24x7

escalation_options  d,u,r

}

 

define hostescalation{

host_name   .*

first_notification  2

last_notification   2

notification_interval   60

contact_groups  support

escalation_period   24x7

escalation_options  d,u,r

}

 

This alerts admins after the interval set on the host/service (5 mins) and
then every hour. On the second alert (5+60 mins) it will alert support (for
the services listed) just the once but then continue to alert admins every
hour.

 

At least that's what I think happens, I'm never sure with esculations!

 

For this to work I had to enable regular expressions and set up service
groups.

 

I have a feeling I also removed the following from my hosts definitions as
well.

 

contact_groups admins

notification_interval 30

notification_period 24x7

notification_options d,r

 

Hope that helps and gives you some ideas.

 

Duncan

 

 

From: Frost, Mark {PBC} [mailto:mark.fro...@pepsico.com] 
Sent: 10 November 2010 17:26
To: 'Nagios Users List'
Subject: [Nagios-users] different notification_intervals by contact

 

So we're setting up some Nagios checks for a new team and they're asking for
something new that I'm not really sure we can do with Nagios.   For any
production alerts they want to receive pager alerts every 15 minutes and
e-mail alerts every 60 minutes.  Since each host/service definition has only
a single notification_interval setting and contact definitions don't allow a
notification_interval setting, I don't see how this can be done within that
context.

 

We don't currently use escalations for anything, but I've been staring at
them and trying to figure out how that might work for us.  In terms of using
escalations to solve this problem I'm struck by several issues:

 

- I'd be trying to use escalations to setup an indefinite pattern, not a
system where there's an last_notification where everyone gets the
notifications.

- I have to do this for a lot of hosts/services and it doesn't look like I
can wildcard service_descriptions (tried it and it failed).

 

My other thought is to just have 2 checks for the same service where check A
has the 15-minute notification_interval and goes to pagers and check B has a
1-hour notification_interval and goes to e-mail.  And that's for a lot of
services.  I can't really do the duplicate checks on hosts.  But either way,
you know, "yuck".

 

I keep thinking there's some easier more obvious solution that's eluding me
to this.  Is something that anyone else has solved?  I'm inclined to tell
them that we can't do this and get them to unify on one
notification_interval like everyone else, but before I do, I thought I'd
ask.

 

 

Thanks

 

Mark


-- 
This message has been scanned for viruses and 
dangerous content by   MailScanner, and is 
believed to be clean. 

--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev___
Nagios-users mailing list
Nagios-users@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

Re: [Nagios-users] SMS Foxbox

2010-11-10 Thread Duncan Berriman
Just a note about volume, that is standard for any sim based device as it is
in effect the same as sending them via a phone and each message takes a few
seconds to send. You could set up a bank of gsm modems like the maestro eco
100 with software of your choice to get round this (even your own software
as it is pretty easy to  do).

As Mark points out an external gateway is a good alternative (like aql.com,
clickatell), perhaps using that for most messages and using the fox box for
messages when your internet connectivity fails.

Duncan

-Original Message-
From: Mark Young [mailto:m...@zarzax.com] 
Sent: 10 November 2010 03:08
To: Nagios Users List
Subject: Re: [Nagios-users] SMS Foxbox

On Nov 5, 2010, at 4:44 AM, Rutger Blom wrote:

> Hello list,
> 
> I was wondering if any of you have experience with using the SMS Foxbox
and Nagios? Are you satisfied with the product? Is there any other solution
you would recommend instead?
> 
> http://www.nagios.org/products/notification/foxbox/
> 
> /Rutger

Hi Rutger,

I originally demoed the SMS FoxBox while working at Nagios Enterprises in
2007.  My original integration attempt was written up on the wiki
http://wiki.nagios.org/index.php/ACME_SYSTEMS_SMSFoxBox.  The device is a
small embedded linux server that takes a SIM card and has a external
antenna.  *It is very important that it has cell (GSM) reception.  Also my
knowledge of the device is now a few years old.

My experience was that it worked very well.  It has the limitation that it
can only send one message at a time (one GSM modem).  My script from the
wiki page used the web api, where you use a web address to send the message
body and recipient.  This was only able to handle a few requests before it
overwhelmed the small web server.  I later created another script that
uploaded messages to a spool directory on the device (using SCP).  This was
able to handle a large number of messages but it takes a long time for the
device to process messages.  I would say if you have over 20 notification
recipients you may want to look for an alternative.  There are web services
that handle these requests (AlarmTilt) or many people now use email
addresses provided by cell providers that text phones
(http://www.emailtextmessages.com/).

I hope that this helps you out.  Good luck in your quest!

Mark Young




--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper David
G. Thomson, author of the best-selling book "Blueprint to a Billion" shares
his insights and actions to help propel your business during the next growth
cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Nagios-users mailing list
Nagios-users@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

--
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.


--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Nagios-users mailing list
Nagios-users@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


Re: [Nagios-users] re-notification problem

2010-10-22 Thread Duncan Berriman
Escalations take over from contacts so your contacts won't be re-advised as
far as I know.

 

By my understanding (which is limited as I've only just implemented
escalations recently) you need to ensure your contacts are included in your
escalations.

 

Duncan

 

From: michal.lacko...@cz.schneider-electric.com
[mailto:michal.lacko...@cz.schneider-electric.com] 
Sent: 22 October 2010 10:52
To: Nagios Users List
Subject: Re: [Nagios-users] re-notification problem

 

The notification appears to work normally if the service escalation config
is omitted. 
Is there any relation between it? 

Michal 







Michal Lackovic/CZ/schnei...@europe 

10/22/2010 10:01 AM 


Please respond to
Nagios Users List 


To

nagios-users@lists.sourceforge.net 


cc



Subject

[Nagios-users] re-notification problem

 






Dear community, 

I just noticed that my system (Nagios 3.2.0) don't re-notify the
contacts.However it sends notification to escalation contacts. 
So what id does is that it sends first notification to the host contact then
after next 4 hours it sends notification to escalation contact and keep
sending every 4 hours. 
As far as I know, if the notification interval is 240 minutes and first
escalation is triggered after 2 notifications are sent to the host contact
then the escalation contact should get first notification after 480 minutes.
Correct? 

My setup: 
First notification to the contacts --> re-notify after 4 hours - re-notify
after 4 hours and and send escalation to leader 

Service template: 

define service { 
  name  Service group 1 
  service_description   24x7,3,10,2 
  max_check_attempts3 
  check_interval10 
  retry_interval2 
  active_checks_enabled 1 
  passive_checks_enabled0 
  check_period  24x7 
  obsess_over_service   0 
  check_freshness   0 
  flap_detection_enabled0 
  notification_interval 240 
  notification_period   24x7 
  notification_options  w,r,c,s 
  notifications_enabled 1 
  register0 


Service definition: 

define service { 
   hostgroup_nameCENTRAL DC, 
   service_descriptionStorage 
   display_nameStorage 
   servicegroupsNRPE agents,Storage 
   useService group 1 
   check_commandcheck_nt_storage!90%!95% 
   host_name!WDEUR01,!WDEUR02 
   register1 
   } 

Escalation definition: 

define serviceescalation {^M 
   hostgroup_name
SLOVAKIA,CZECH,POLAND,BULGARIA,GREECE,!GATEWAY 
   service_description .* 
   contactsNorthern CEE EUO leader 
   first_notification  2 
   last_notification   0 
   notification_interval   240 
   escalation_period   24x7 
   escalation_options  w,c 
   }   

thanks in advance for your advice 

Michal 
__
This email has been scanned by the MessageLabs Email Security System.
__--

Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
 
http://p.sf.net/sfu/nokia-dev2dev___

Nagios-users mailing list
Nagios-users@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 

-- 
This message has been scanned for viruses and 
dangerous content by   MailScanner, and is 
believed to be clean. 

--
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total 

Re: [Nagios-users] Wildcards in hostgroup definitions

2010-10-21 Thread Duncan Berriman
Looks ok to me  - my test was

define hostgroup{
hostgroup_name  ALL-SERVERS ; The name of the hostgroup
alias  ALL-SERVERS ; The name of the hostgroup
hostgroup_members .*
}

That parses ok but I end up with nothing in the group when I look at the
nagios display.

If I use individual members it works and they appear in the nagios display.

Looks like it doesn't work at any rate. 

I just upgrade to the latest version as I was having issues with wildcards
but I think that was more down to my understanding. I've been trying to use
them for escalations. I think I finally got there (I think - time will tell)
but I had to add a lot of service groups to make it work the way I wanted.

Duncan

-Original Message-
From: olourkin-nag...@yahoo.com [mailto:olourkin-nag...@yahoo.com] 
Sent: 21 October 2010 17:07
To: Nagios Users List
Subject: Re: [Nagios-users] Wildcards in hostgroup definitions

Thanks for checking it out, Duncan.  Here are the config snippets to
illustrate the mystery:

define hostgroup {
hostgroup_name  ecomUs
alias   ecom servers - US
members .*
}

- This works.  We get an ecomUs hostgroup with all our hosts.


define hostgroup {
hostgroup_name  ecomUs
aliasecom servers - US
hostgroup_members   .*
}

- This doesn't work.  We get this error after running a config verification:

 "Error: Could not find member group '.*' specified in hostgroup (config
file '/etc/nagios/conf.d/tier12/env-specific/vdev/hostgroup.d/ecomUs.cfg',
starting on line 7)."

Cheers,
Erik


- Original Message 
From: Duncan Berriman 
To: Nagios Users List 
Sent: Thu, October 21, 2010 2:11:44 AM
Subject: Re: [Nagios-users] Wildcards in hostgroup definitions

Hi Erik,

Appears to work just fine for me if I am testing your case correctly.

Perhaps you could post the config file (or snip of) that's causing the
issue.

Duncan

-Original Message-
From: olourkin-nag...@yahoo.com [mailto:olourkin-nag...@yahoo.com]
Sent: 20 October 2010 22:45
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] Wildcards in hostgroup definitions

Hi all -

Got a mystery regarding the use of regex matching that I hope someone on the
listserv might clear.  We have the appropriate config options to use regex,
and 
it works just fine for the members directive - ie. "members.*" expands
just
as we'd expect.  

But "hostgroup_members.*" returns an error along the lines of "Could not

find member group '.*' specified in hostgroup", leading us to believe
that Nagios is simply ignoring regex matching for the hostgroup_members
directive. 
Anyone know if we're off our rockers, or if Nagios really does handle things
this way?

Thanks,
Erik Larkin



--
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
___
Nagios-users mailing list
Nagios-users@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

--
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.



--
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
___
Nagios-users mailing list
Nagios-users@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



--
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
__

Re: [Nagios-users] Wildcards in hostgroup definitions

2010-10-21 Thread Duncan Berriman
.* is correct that's a proper regex expression.

Duncan

-Original Message-
From: Assaf Flatto [mailto:nag...@flatto.net] 
Sent: 21 October 2010 17:10
To: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Wildcards in hostgroup definitions

  Why do you have the '.' before the '*' ?

is that on purpose or just  a tab representation ?

Try removing the '.' and test again .

Assaf


On 21/10/10 17:07, olourkin-nag...@yahoo.com wrote:
> Thanks for checking it out, Duncan.  Here are the config snippets to 
> illustrate the mystery:
>
> define hostgroup {
>  hostgroup_name  ecomUs
>  alias   ecom servers - US
>  members .*
> }
>
> - This works.  We get an ecomUs hostgroup with all our hosts.
>
>
> define hostgroup {
>  hostgroup_name  ecomUs
>  aliasecom servers - US
>  hostgroup_members   .*
> }
>
> - This doesn't work.  We get this error after running a config
verification:
>   "Error: Could not find member group '.*' specified in hostgroup 
> (config file 
> '/etc/nagios/conf.d/tier12/env-specific/vdev/hostgroup.d/ecomUs.cfg',
starting on line 7)."
>
> Cheers,
> Erik
>
>
> - Original Message 
> From: Duncan Berriman
> To: Nagios Users List
> Sent: Thu, October 21, 2010 2:11:44 AM
> Subject: Re: [Nagios-users] Wildcards in hostgroup definitions
>
> Hi Erik,
>
> Appears to work just fine for me if I am testing your case correctly.
>
> Perhaps you could post the config file (or snip of) that's causing the 
> issue.
>
> Duncan
>
> -Original Message-
> From: olourkin-nag...@yahoo.com [mailto:olourkin-nag...@yahoo.com]
> Sent: 20 October 2010 22:45
> To: nagios-users@lists.sourceforge.net
> Subject: [Nagios-users] Wildcards in hostgroup definitions
>
> Hi all -
>
> Got a mystery regarding the use of regex matching that I hope someone 
> on the listserv might clear.  We have the appropriate config options 
> to use regex, and
> it works just fine for the members directive - ie. "members.*" expands
> just
> as we'd expect.
>
> But "hostgroup_members.*" returns an error along the lines of "Could
not
>
> find member group '.*' specified in hostgroup", leading us to 
> believe that Nagios is simply ignoring regex matching for the 
> hostgroup_members directive.
> Anyone know if we're off our rockers, or if Nagios really does handle 
> things this way?
>
> Thanks,
> Erik Larkin
>

--
Never,Ever Cut A Deal With a Dragon


Next year I will be doing the London to Paris bike ride to
raise money for the DogTrust (www.dogstrust.co.uk) .
Please Sponsor me at http://www.justgiving.com/Assaf-Flatto



--
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev
___
Nagios-users mailing list
Nagios-users@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

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev
___
Nagios-users mailing list
Nagios-users@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


Re: [Nagios-users] Wildcards in hostgroup definitions

2010-10-21 Thread Duncan Berriman
Hi Erik,

Appears to work just fine for me if I am testing your case correctly.

Perhaps you could post the config file (or snip of) that's causing the
issue.

Duncan

-Original Message-
From: olourkin-nag...@yahoo.com [mailto:olourkin-nag...@yahoo.com] 
Sent: 20 October 2010 22:45
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] Wildcards in hostgroup definitions

Hi all -

Got a mystery regarding the use of regex matching that I hope someone on the
listserv might clear.  We have the appropriate config options to use regex,
and 
it works just fine for the members directive - ie. "members.*" expands
just 
as we'd expect.  

But "hostgroup_members.*" returns an error along the lines of "Could not

find member group '.*' specified in hostgroup", leading us to believe
that Nagios is simply ignoring regex matching for the hostgroup_members
directive. 
 Anyone know if we're off our rockers, or if Nagios really does handle
things this way?

Thanks,
Erik Larkin



--
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
___
Nagios-users mailing list
Nagios-users@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

--
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.


--
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev
___
Nagios-users mailing list
Nagios-users@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


[Nagios-users] Wildcard Escalations

2010-10-20 Thread Duncan Berriman
Hi,

 

There seems to be some issues with Service Escalations and wildcards.

 

If you use wildcards on hosts every host has to have a service associated
with it otherwise the configuration does not validate.

 

Example

 

define serviceescalation{

host_name   .*

service_description .*

first_notification  1

last_notification   99

notification_interval   60

contact_groups  admins

escalation_period   24x7

escalation_options  w,u,c,r

}

 

Causes 

 

Error: Could not find a service matching host name 'pix' and description
'.*'

 

I got round that by creating a dummy service for items like firewalls and
routers which have no service as below.

 

define service{

use generic-service

# Hostname of remote system

host_name pix

service_description dummy

is_volatile 0

check_period 24x7

max_check_attempts 1

normal_check_interval 5

retry_check_interval 1

check_command check-dummy

}

 

Now I am trying to use wildcards on the service names within the
escalations, the validation fails on any host that does not have a service
that matches the wildcard.

 

define serviceescalation{

host_name   .*

service_description .*Bandwidth.*

first_notification  2

last_notification   2

notification_interval   60

contact_groups  support

escalation_period   24x7

escalation_options  w,u,c,r

}

 

Causes

 

Error: Could not find a service matching host name 'pix' and description
'.*Bandwidth.*

 

Why when a wildcard is in use should every host have to have a service and
every host have to have a service matching the wildcard? It makes no sense
(to me at least).

Is this a bug or is it designed to work this way? 

 

Is there any way to turn off these checks as they appear to me at least
incorrect and pointless?

 

Thanks

Duncan

 

 

 

--
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev___
Nagios-users mailing list
Nagios-users@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