Out of Date Host Alias and Display Name

[bvinisky]

Hi There,

I have a bunch of hosts that I make periodic bulk modifications to their host parameters. We have alternating production/staging environments. So when staging gets elevated to production and production is demoted to staging, I accommodate in Nagios by flipping IPs between prd/stg. All staging IPs get assigned to production hosts and visa versa.

In addition to the IP change, I have the host description and alias modified to list the 'true' host name of the server, not the hostname that Nagios tracks it by. However, I've noticed that for some hosts, the emails do not always contain the new, accurate alias. If I look the host up in the NagiosXI CCM, they have the correct alias. If I look the host up in Nagiosql it also has the correct alias. If I look at the host file produced in /usr/local/nagios/etc/hosts/ it contains the proper alias. However, emails still come through with the wrong alias. The retention.dat file holds the wrong/old alias and display_name (description). I haven't removed this file completely, but I have tried deleting the individual alias and display_name entries and the full host block, but it gets regenerated with the old data. The backend API also reports the old alias when I check it.

This isn't happening with all hosts that are rotated in this manner, only about 30% or so. What's holding the bad/old alias entry and how do I get it updated?

Thanks,

Bryant

[nagiosadmin42]

Bryant,

I've encountered similar issues in the past, and at one point tracked down the stale host information as coming from the "nagios" database. At that point, since I'm not sure about the interaction between the "nagios" and "nagiosql" databases, we decided to live with the inconsistency.

Alan

[mguthrie]

What version of Nagios XI are you using?

[nagiosadmin42]

We encountered this problem during our initial evaluation of NagiosXI back on xi-2011r2.1 or xi-2011r2.2. I don't know if it's still an issue on R3.3, as our host definitions have stabilized and we don't modify them very often.

Alan Edel

[bvinisky]

Ah, yes we're running 2011R2.2. I take it there might be a fix for this in the latest release(s)? Regardless, I'll plan to work in the upgrade soon.

Bryant

[scottwilkerson]

Yes. this was a bug that was resolved in all versions newer than 2011R3.0