Issue with renaming tool

[WillemDH]

Hello,

When I rename a host that has attached services, I get errors when applying configuration afterwards:

renamed weather_gent_poortakker to weather_gent , then applied =>
Error: Could not find any host matching 'weather_gent_poortakker' (config file '/usr/local/nagios/etc/services/gent_poortakker_precip.cfg', starting on line 16)
Error: Failed to expand host list 'weather_gent_poortakker' for service 'gent_poortakker_precip' (/usr/local/nagios/etc/services/gent_poortakker_precip.cfg:16)

Got it very time.
This does not seem normal.

Grtz

Willem

[tmcdonald]

Seems somewhat ghost-hosty. What XI version is this?

[lmiltchev]

I was able to recreate it and filed an internal bug report (NEW TASK ID 3864).

[WillemDH]

Thanks Ludmill for confirming I'm not crazy.

Version is R1.4

Grtz

[lmiltchev]

[WillemDH]

Hello,

I'm experiencing similar issues when trying to rename a host without the renaming tool:

Code: Select all

Error: Could not find any host matching 'server1' (config file '/usr/local/nagios/etc/services/server1.cfg', starting on line 55)
Error: Failed to expand host list 'server1' for service 'SVC_Solr_Updates' (/usr/local/nagios/etc/services/server1.cfg:55)
   Error processing object config files!

Is there any solution for this issue, I have multiple hosts waiting to be renamed...

Grtz

Willem

[lmiltchev]

It is a bug. I added a note to the bug report I filed for the "Renaming Tool". I will talk to our developers to see if they can give this a "higher" priority.

[lmiltchev]

Actually, this behavior is caused by not writing ALL of the configs when applying configuration (in XI 2014).
This change made applying configuration a log faster, especially for large environments, but it seemed to create an issue in this case...
As a workaround you can try running the Write Config Tool. Hit the "Delete" button first, then "Write", "Verify", and apply configuration.
Edit: Apply Config will also fail after renaming a host via the Renaming Tool IF the host and its services have DIFFERENT config names.

[b2m]

Actually, this behavior is caused by not writing ALL of the configs when applying configuration (in XI 2014).
This change made applying configuration a log faster, especially for large environments, but it seemed to create an issue in this case...
As a workaround you can try running the Write Config Tool. Hit the "Delete" button first, then "Write", "Verify", and apply configuration.
Edit: Apply Config will also fail after renaming a host via the Renaming Tool IF the host and its services have DIFFERENT config names.

Had the same problem and I can confirm the workaround.

[abrist]

The only way this issue should happen at the moment is if your services' config names are different than the hostname. Can others confirm?