One particular host renders hostgroup unviewable in XI

[hhlodge]

I just added a bunch of hosts via Tools->Import method. All the configs were built by a script and template file from another host already in XI. I added 41 hosts to a hostgroup and this hostgroup would start to present the title and navigation icons (pin and delete) in the dashlet but no content. I finally narrowed it down to one particular host in the hostgroup. I've demonstrated it several times. Put this host in, no hostgroup data population. Take it out, all the other 40 hosts show. I can move any others in and out without issue. It was imported right along with the others and is identical to many except for its name and IP address. This happens in Views, Home, Hostgroup Summary, everywhere. I'm at a loss here. Any thoughts? Here's the config FWIW.

# cat NOPRTSAC01A.cfg
define host {
host_name NOPRTSAC01A
use xiwizard_windowswmi_host
address 10.10.2.170
parents sw10-10-0-240
max_check_attempts 3
check_interval 5
retry_interval 1
check_period xi_timeperiod_24x7
contact_groups is,it-admins
notification_interval 60
notification_period xi_timeperiod_24x7
icon_image windowsxp.png
statusmap_image win_server.png
_xiwizard windowswmi
register 1
}

define service {
host_name NOPRTSAC01A
service_description CPU Usage
use xiwizard_windowswmi_service
check_command check_xi_service_wmiplus!checkcpu!-w 80 -c 90!!!!!!
max_check_attempts 3
check_interval 10
retry_interval 3
notification_interval 60
contact_groups is,it-admins
_xiwizard windowswmi
register 1
}

define service {
host_name NOPRTSAC01A
service_description Drive C:
use xiwizard_windowswmi_service
check_command check_xi_service_wmiplus!checkdrivesize!-a C: -w 80 -c 95!!!!!!
max_check_attempts 3
check_interval 10
retry_interval 1
notification_interval 240
contact_groups is,it-admins
_xiwizard windowswmi
register 1
}

define service {
host_name NOPRTSAC01A
service_description Eventlog - Application
use xiwizard_windowswmi_service
check_command check_xi_service_wmiplus!checkeventlog!-a Application -o 1 -3 1 -w 0
max_check_attempts 3
check_interval 10
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
contact_groups is,it-admins
_xiwizard windowswmi
register 1
}

define service {
host_name NOPRTSAC01A
service_description Eventlog - System
use xiwizard_windowswmi_service
check_command check_xi_service_wmiplus!checkeventlog!-a System -o 2 -3 1 -c 0
max_check_attempts 3
check_interval 10
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
contact_groups is,it-admins
_xiwizard windowswmi
register 1
}

define service {
host_name NOPRTSAC01A
service_description Memory Usage
use xiwizard_windowswmi_service
check_command check_xi_service_wmiplus!checkmem!-a physical -w 80 -c 90!!!!!!
max_check_attempts 3
check_interval 10
retry_interval 1
notification_interval 240
contact_groups is,it-admins
_xiwizard windowswmi
register 1
}

define service {
host_name NOPRTSAC01A
service_description Page File Usage
use xiwizard_windowswmi_service
check_command check_xi_service_wmiplus!checkmem!-a page -w 80 -c 90
max_check_attempts 3
check_interval 10
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
contact_groups is,it-admins
_xiwizard windowswmi
register 1
}

define service {
host_name NOPRTSAC01A
service_description Ping
use xiwizard_windowsserver_ping_service
max_check_attempts 3
check_interval 5
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
contact_groups is,it-admins
_xiwizard windowswmi
register 1
}

[mguthrie]

Can you check what happens if you rename the host?

Also, does the hostgroup with this host added display correctly in the Core interface? http://<yourserver>/nagios

[hhlodge]

They do indeed all show in the hostgroup in Nagios core. Something else is up though as I had removed all the hosts and services and added them back by import and now it's not that particular host causing the hostgroup contents to vanish, it's not visible even with that host removed from the hostgroup. I am removing and adding back various other hosts to try and nail it down to no avail.

[hhlodge]

Something else is up. I was seeing this issue with Firefox 4 on Windows XP. I went to try Firefox 3.6.8 on Ubuntu 10.4 and IE8 on Windows XP and there's just a spinning wheel on that dashlet that never times out.

XI.png

[mguthrie]

I hate asking this, but can you try rebooting the XI server and see if the issue still exists?

If it's a production server and you'd prefer not to reboot, try the following commands.

Code: Select all

killall -9 nagios
killall -9 ndo2db
service mysqld restart
service ndo2db start
service nagios start

[hhlodge]

I did the latter and then a reboot to no avail. Also, on the home page, I get a spinning wheel on the Status Summary For All Host Groups dashlet; i.e none of then show. If I go into Hostgroup Overview, the others show and only the problematic hostgroup dashlet spins.

[mguthrie]

Are you able to view the service status details for all of the services for this host? We had an issue a while back where some binary data was being returned from a custom plugin and it was breaking the XML generation XI.

[hhlodge]

I am and again, I don't think it's this host now. All of them are from the same .cfg template file, created with sed and a hostname:IP table file for values. It seems more like a limit on the number of hosts but it isn't constant. Sometimes 40 will show, sometimes 38 won't.

[hhlodge]

I just created 50 new hosts with just a ping service and a hostgroup with all 50 is fully visible, so it may be the sum of services. I will concentrate on if more services causes it or finding what in my other hosts or services might be triggering the issue.

[mguthrie]

Something else to try would be to access the Admin->Performance Settings page and changed the hostgroups to "unified hostgroups," which will give you a different view that may work in the meantime. At the moment we're not able to recreate what you're experiencing, but if you happen to nail down some sort of recreatable pattern, we'll definitely go after it and see what we can figure out.