Old config files persist after renaming hosts

[awoodewh]

I renamed several hosts to make them standard with our naming convention. Now, the old host and service configs persist, but do not show up in Core or XI, unless they alarm....but then the show up a double entries.

I've tried deleting the service and host entries, but when I apply the configuration they return. Is there a way to remove them without modifying the database directly. I tried searching for this issue in the forum, but did not see this issue.

Thanks,
Andy

[rdedon]

Hmm, lets try this to start:

If you have successfully deleted a host and all of it's services from the Core Config Manager, but you're still seeing it in the status tables, then you most likely have multiple instances of Nagios running on your machine. To make sure all instances are stopped, type the following in the command-line.

Code: Select all

killall nagios
 service nagios start

[awoodewh]

Thanks, I figured it out. The host name and service name have to match case. Once I changed all the service names to match the host name I was able to remove both the host and services.

I had changed EWHServer123 to ewhserver123, but failed to change the service names to match.

Thanks,
Andy

[mguthrie]

Awesome, glad it's working again!

[griffithusg]

Does this mean that a name change does not have a flow on effect to the services that are being monitored?

[rdedon]

If you change your host name your services would need to point to that new host name.