Nagios Support Forum

If you've got actual config files for hosts and services in your /usr/local/nagios/etc directory that should not be there, and are not listed in the Core Config Manager, go ahead and delete the files. Once in a while NagiosQL will somehow lose track of a config file and it will just sit there without being updated or deleted. A general rule is that if it's in the Core Config Manager, it's in the database and it can always be written out to the file. But if you've got a config that's outside of the etc/static directory that isn't anywhere to be found in the CCM then that's probably going to cause unpredictable results.

The way the CCM works is that it store the configuration data in the mysql DB, and then when you "Apply Configuration," the DB info gets written to the configuration files. Nagios runs the config verification on the actual config files, and the config files are what Nagios is actually using. The CCM is simply a web UI for managing the config files.

I have tried to delete them from /usr/local/nagios/etc but everytime I app conf from nagios XI it comes back

This is what I did and it seems to have worked

I deleted chicondb1_server.cfg
Then I created another chicondb1_server through nagios XI
I then went to tools and ran those selections
I checked and chicondb1_server.cfg was out in the directory
I then did an apply config in nagios XI and it left alone the chicondb1_server.cfg file
I then removed chicondb1_server service using nagios XI
And it was gone

We will see if this works everytime I have issues

Thanks

Thanks for the report!