[Nagiosplug-help] Host monitoring

[Grant Lowe]

Hi Andy,

Here's my host definition:

define host {
host_name                         myhost
alias                             myhost
display_name                      My Host
address                           172.20.8.215
hostgroups                        solaris-servers
check_command                     check-host-alive
initial_state                     o
max_check_attempts                5
check_interval                    3
retry_interval                    3600
active_checks_enabled             0
passive_checks_enabled            1
check_period                      24x7
obsess_over_host                  0
check_freshness                   0
event_handler_enabled             0
flap_detection_enabled            0
flap_detection_options            o,d,u
process_perf_data                 1
retain_status_information         1
retain_nonstatus_information      0
contacts                          glowe
notification_interval             300
notification_period               24x7
notification_options              d,u,r,f,s
notifications_enabled             1
stalking_options
}


Here's my service definition:

define service{
host_name                       blarney
hostgroup_name                  solaris-servers
service_description             Ping
check_command                   check_ping!200.0,20%!600.0,60%
max_check_attempts              5
notification_interval           60
check_period                    24x7
}

Thanks for the help!


----- Original Message ----
From: Andy Shellam <andy-lists at networkmail.eu>
To: Grant Lowe <glowe at sbcglobal.net>
Cc: nagiosplug-help at lists.sourceforge.net
Sent: Monday, October 20, 2008 1:44:21 PM
Subject: Re: [Nagiosplug-help] Host monitoring

Hi Grant,

Have a look at your contact definition, at the service and host 
notification commands - look those up in your commands.cfg (or whatever 
your command file is) and that should point to a command_line that sends 
the e-mail (using /bin/mail or similar.)  It may even be a shell 
script.  Either way, we'd need to see your command definition to try and 
work out what's going on here.

Andy

Grant Lowe wrote:
> Hi Andy,
>
> I'm looking at all the command definitions and nothing is in there that I can see about retaining PROBLEM data.  I do have the notifications set to 60 minutes and that's when I receive the email.  But it always says PROBLEM in the email I receive.  Maybe that's the problem?  Is there a way to set it to a different string?  Or is that opening up a can of worms?
>
>
>
> ----- Original Message ----
> From: Andy Shellam <andy-lists at networkmail.eu>
> To: Grant Lowe <glowe at sbcglobal.net>
> Cc: nagiosplug-help at lists.sourceforge.net
> Sent: Monday, October 20, 2008 11:34:05 AM
> Subject: Re: [Nagiosplug-help] Host monitoring
>
> Hi Grant,
>
> What are your notification options for the host, and your notification 
> command?  It's possible that the host/s in question has gone down and 
> Nagios is reporting it has returned to an UP state, but your 
> notification command is hard-coded to say PROBLEM.
>
> Thanks,
>
> Andy
>
> Grant Lowe wrote:
>  
>> Hi All,
>>
>> Another question for you all.  On some hosts, I keep on getting a notification that reads:
>>
>> ** PROBLEM Host Alert: myserver is UP **
>>
>> I'm trying to figure out why Nagios is generating these errors, when the host is obviously up.  Thanks!
>>
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
>> Build the coolest Linux based applications with Moblin SDK & win great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Nagiosplug-help mailing list
>> Nagiosplug-help at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
>> ::: Please include plugins version (-v) and OS when reporting any issue. 
>> ::: Messages without supporting info will risk being sent to /dev/null
>>  
>>    
>
>
>