Nagios Support Forum

This is Nagios XI 2011R2.2

We had an Ubuntu server named 'Eng001' and had to re-install the O.S. When we entered the system name during the install, we forgot and used 'ENG001' in upper case.

Nagios stopped recognizing some of the services, so I went in and deleted all the services for the old host name and renamed the host in upper case using the Core Config Manager, then applied changes.

I re-added the services for the renamed host, and the Core Config Manager shows everything with the new upper-case name.

However, when I go to the Nagios XI dashboard, the host still shows with the old mixed-case name, and some of the passive services still aren't being recognized, they show as "PENDING".

Rebooting didn't help. I've hunted through the filesystem and deleted old .cfg files with the old host name, however there's still something missing... any ideas?

Also, the Nagios "Host Detail" dashboard report shows entries for BOTH the old and new host names, e.g. Eng001 and ENG001. Obviously, something's cached, I just don't know where or how to clean it up.

I've been pulling my hair out for the past several hours, trying to figure out this host naming problem. I was poking around, looking at the config files in /usr/local/nagios/etc/hosts, and noticed that the file for ENG001 existed, and that there was NO file for Eng001. This is as I expected, and as it should be.

However, while I was there, I noticed that ENG001's cfg file had an entry for "_xiwizard linux-server" that my other Ubuntu hosts do not. So on a whim, I went to the Core Config Manager, selected the Host entry for ENG001, clicked on its Misc tab, and deleted the Free Variable Definitions entry for _xiwizard. I applied changes, verified that the config snapshot output didn't contain any errors, and went back to the Hosts dashboard. All of a sudden the mixed-case entry no longer appeared, and when I clicked on the upper-case entry, its passive services were there and had performance data!! Suddenly all is well, however all I can say is: WTF???

That is strange indeed.

My only guess would be some sort of caching, but really I'm just as at a loss with this as you are.