Host Checks NEVER Happen

[Matthew Jurgens]

I have found the answer to this after reading the documentation!

Make sure that the host defination includes the following:
check_command                        check-host-alive


For some reason the sample configs I had based my config on did not have 
this config item for hosts.

Matthew Jurgens wrote:
> define  host {
>        name                       std_host
>        max_check_attempts              2
>        active_checks_enabled           1
>        passive_checks_enabled          1
>        check_period                    24x7
>        obsess_over_host                1
>        check_freshness                 0
>        event_handler_enabled           1
>        flap_detection_enabled          1
>        process_perf_data               0
>        retain_status_information       1
>        retain_nonstatus_information    1
>        contact_groups                  admin
>        notification_interval           1
>        notification_period             24x7
>        notification_options            d,u,r,f
>        notifications_enabled           1
>        register                        0
>        }
>
> define  host {
>            use std_host
>        host_name                       noddy
>        alias                           noddy
>        address                         192.168.0.78
>        }
>
> define  service {
>    name    std_service
>    hostgroup_name            gw
>    is_volatile            0
>    max_check_attempts        2
>    normal_check_interval        1
>    retry_check_interval        1
>    active_checks_enabled        1
>    passive_checks_enabled        1
>    check_period            24x7
>    parallelize_check        1
>    obsess_over_service        1
>    check_freshness            0
>    event_handler_enabled        1
>    flap_detection_enabled        1
>    process_perf_data        1
>    retain_status_information    1
>    retain_nonstatus_information    1
>    contact_groups            admin
>    notification_interval        240
>    notification_period        24x7
>    notification_options        w,u,c,r,f
>    notifications_enabled        1
>    register            0   ; DONT REGISTER THIS DEFINITION - ITS NOT A 
> REAL SERVICE, JUST A TEMPLATE!
>    }
>   define  service {
>    name    std_service
>    hostgroup_name            gw
>    is_volatile            0
>    max_check_attempts        2
>    normal_check_interval        1
>    retry_check_interval        1
>    active_checks_enabled        1
>    passive_checks_enabled        1
>    check_period            24x7
>    parallelize_check        1
>    obsess_over_service        1
>    check_freshness            0
>    event_handler_enabled        1
>    flap_detection_enabled        1
>    process_perf_data        1
>    retain_status_information    1
>    retain_nonstatus_information    1
>    contact_groups            admin
>    notification_interval        240
>    notification_period        24x7
>    notification_options        w,u,c,r,f
>    notifications_enabled        1
>    register            0   ; DONT REGISTER THIS DEFINITION - ITS NOT A 
> REAL SERVICE, JUST A TEMPLATE!
>    }
>  
> define  service {
>    use std_service
>    host_name            noddy
>    service_description    HTTP Admin
>    check_command            check_http
>    }  
>
>
> Jim Perrin wrote:
>> On 5/8/06, Matthew Jurgens <nagios at edcint.co.nz> wrote:
>>> I've installed a basic Nagios 2 config. I have 50 service checks 
>>> working
>>> perfectly and 12 hosts.
>>> Even when services on a host go down host checks never seem to be 
>>> executed.
>>> I've setup network packet captures to see if pings leave the Nagios 
>>> host
>>> but they never do.
>>>
>>> I created a host with an IP address that does not exist and one 
>>> service.
>>> This service will of course go Hard critical after a couple of checks.
>>> It does and I get notified and Nagios still maintains that the host 
>>> is UP!
>>>
>>> Can anyone provide any hints as to why Nagios does this? What can I 
>>> check?
>>
>> You should check your host configs. Or you can provide a bit more
>> detail here about how you have your host configs set up and we can
>> help.
>> -- 
>> This message has been double ROT13 encoded for security. Anyone other
>> than the intended recipient attempting to decode this message will be
>> in violation of the DMCA
>>
>>
>> -------------------------------------------------------
>> Using Tomcat but need to do more? Need to support web services, 
>> security?
>> Get stuff done quickly with pre-integrated technology to make your 
>> job easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
>> Geronimo
>> http://sel.as-us.falkag.net/sel?cmd_______________________________________________ 
>>
>> 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
>>
>


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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