Host files not being updated on reconfigure

[Fred Kroeger]

Hi came across a small issue with the latest version of NagiosXI.
I had a number of hosts as members of HostGroup-A
I changed the name of HostGroup-A to HostGroup-B. Checked the host entries in CCM and they were all members of HostGroup-B as expected.
I ran the configure and it failed as the host files weren't updated and it was complaining that it couldn't find HostGroup-A which was still being refernced in each hosts cfg file.

The work-around for me was to manually delete all the host cfg files that contained the HostGroup-A entry - Configure then worked fine.

regards... Fred

[tmcdonald]

I ran the configure and it failed as the host files weren't updated and it was complaining that it couldn't find HostGroup-A which was still being refernced in each hosts cfg file.

What specifically do you mean? Did you click Apply Config or did you run the reconfigure script from the command line?

And just to confirm, this is on 2014 R1.1?

[Fred Kroeger]

Yes this is on R1.1
I used Apply Configuration from the GUI

So the sequence was

1) Rename a HostGroup via CCM
2) Apply Config via CCM - this failed as all the hosts cfg file had not been updated and still referenced the old HostGroup
3) Manually deleted all the cfg files that contained the old HostGroup name
4) Reran Apply Config via CCM - completed successfully

regards... Fred

[lmiltchev]

I can verify the bug. It works "one way" only. If you added members to a hostgroup (CCM->Host Groups->Manage Hosts), then rename the hostgroup, the Apply Configuration *shouldn't fail". However, if you add a host to a hostgroup (CCM->Hosts->Manage Hostgroups), then rename the hostgroup, the Apply Configuration fails. In any case, this is a bug, which will be fixed in the next release of XI. I believe, if you followed the steps, outlined in this post, this would fix the issue for you.

[Fred Kroeger]

Thanks for checking - you can can close this thread. Do the updates fix anything else ?

Fred

[lmiltchev]

I don't think so. In any case, we have several bug fixes in R1.2, including this one, which is coming very soon (maybe today ). I am locking this thread.