Hosts will not delete and graph data not updating

[snapon_admin]

I have 4 hosts that I have deleted from the config using CCM. They do not appear in CCM anymore, but when I search for them in the GUI they are there. All the services for 3 of these hosts have successfully been removed, but I cannot delete the hosts because they do not appear in CCM and when I try to delete from the config page I get an error stating that no record can be found in the config file for that host. One of the hosts still has all the services show up when viewed in the GUI, but they do not show up in CCM and cannot be removed either.

I am also experiencing an unrelated issue where none of my graphs are displaying data, for any host or service. This has happened to us before and, in the past, a server reboot has corrected the graph data issue. This time it did not. I have sent an email to xisupport about that issue, though. I just felt it worth mentioning in case anyone here has any thoughts on that as well. I am supposed to be giving a demo of our Nagios environment tomorrow, and with no graph data and some stuck hosts it's not likely to be a very good demo. The graph data stopped updating this past Sunday (10.6), and it appears that data is still being collected, just not updating the graphs.

Running Nagios XI 2012R2.4 on CentOS running on a VM.

[tmcdonald]

Ghost Hosts!

http://support.nagios.com/wiki/index.ph ... t_Hosts.29

For your first issue, hunt the ghost config files down in /usr/local/nagios/etc/hosts and delete them manually. Then in CCM, go to Core Config Manager->Write Config Tool. Don't apply config yet! Verify that they are gone and everything is good, then you can apply.

Let's handle this then work on the graphs.

[snapon_admin]

Holy useful FAQ...how have I never seen this before? Definitely bookmarked for later. Anyway, that did it, thanks! As for the graphs, I have a support agent working with me on that as we speak, so I think it's safe to lock this one up. Thanks again!

[tmcdonald]

Not a problem at all. I actually had this exact ghost host problem a few times at my previous job, so I am a bit of a *sunglasses on* Ghost Buster.