Unreachable Hosts fail to update

[GreatWolfResorts]

We're noticing a problem with our Nagios XI system, that when hosts drop into an unreachable state, they fail to successfully return to an OK state after their parent object recovers. The "next check" timer appears to updated, but the "last check" does not. If I force an immediate check, it will update and return to an "OK" state. I've also restarted the Nagios, NDO2DB and MySQLD services which temporarily resolve the issue. Eventually the bug crops up again.

At present, I have four hosts listed as unreachable. I am able to successfully ping these devices from the Nagios server via the command console.

[slansing]

These are actual hosts and not services running passive checks correct? Do their services return to an OK state after you are able to ping the host again? If you run an active check by "clicking Schedule an immediate check from the Host Details Page" Are you able to update the last check time in the details box? Under Home > Monitoring Process > Performance, can you send an image of the dashlet on the right side titled "Monitoring Engine Performance."

[GreatWolfResorts]

These are active host checks. The services for the host return to an "OK" state when the device can be pinged by the server. It's just the host itself that remains in an "Unreachable" state. An immediate check on the host updates the "last check" time and returns the state of the host to "OK."

[scottwilkerson]

What is the check frequency for these hosts? Also, could you post the config for one of these hosts as well as a copy of any templates applied.

Thanks.

[GreatWolfResorts]

Here is the host configuration file for one of them. Check frequency included:

Code: Select all

###############################################################################
#
# Host configuration file
#
# Created by: Nagios QL Version 3.0.3
# Date:       2013-05-09 13:46:36
# Version:    Nagios 3.x config file
#
# --- DO NOT EDIT THIS FILE BY HAND ---
# Nagios QL will overwite all manual settings during the next update
#
###############################################################################

define host {
        host_name                       WI-CMO
        use                             xiwizard_windowsserver_host
        address                         ###.###.###.###
        parents                         WI-SW1
        hostgroups                      WI-Servers
        max_check_attempts              5
        check_interval                  5
        retry_interval                  1
        check_period                    24x7
        contact_groups                  WI_IT
        notification_interval           0
        notification_period             24x7
        first_notification_delay        0
        notification_options            d,r,f
        notifications_enabled           1
        icon_image                      win_server.png
        statusmap_image                 win_server.png
        register                        1
        }

###############################################################################
#
# Host configuration file
#
# END OF FILE
#
###############################################################################

Host template used (very basic):

Code: Select all

define host {
       name                                     xiwizard_windowsserver_host
       check_command                            check_xi_host_ping!3000.0!80%!5000.0!100%
       use                                      xiwizard_generic_host
       register                                 0

}

[lmiltchev]

I would be easier to solve your issue if you sent an email to [email protected]. Once, you open a new ticket in our system, we can schedule a time for a remote session and take a closer look at your system. Put "Re: Unreachable Hosts fail to update" in the email subject. Thank you!

[GreatWolfResorts]

E-mail Submitted.