We currently are having issues with the Bulk Host Cloning and Import tool. We have worked through some troubleshooting steps shown here: https://support.nagios.com/forum/viewto ... 16&t=49855
When we go through and verify the files, it throws an error and says that there are errors with max_check_attempts in other machines. It looks like this is overwriting existing good config files, but we aren't sure how we should fix this.
Issue with Bulk Host Cloning and Import
-
benjaminsmith
- Posts: 5324
- Joined: Wed Aug 22, 2018 4:39 pm
- Location: saint paul
Re: Issue with Bulk Host Cloning and Import
Hi @gcox,
If you are getting an error verifying configs, there maybe some incomplete hosts/services from running the Bulk Host Cloning wizard. As noted in the other post, there was a minor format change to the object configuration data format in updated versions, so before using the Bulk Host Cloning and Import wizard, it's necessary to go to the CCM > Config File Management and reset the configs:
Delete Files
Write Configs
Verify Files
Restart Nagios Core
You don't need to worry about overwriting existing good config files, as Write Configs only rewrites the object.cache file used to access config data.
Please let me now if you able to resolve the issue.
If you are getting an error verifying configs, there maybe some incomplete hosts/services from running the Bulk Host Cloning wizard. As noted in the other post, there was a minor format change to the object configuration data format in updated versions, so before using the Bulk Host Cloning and Import wizard, it's necessary to go to the CCM > Config File Management and reset the configs:
Delete Files
Write Configs
Verify Files
Restart Nagios Core
You don't need to worry about overwriting existing good config files, as Write Configs only rewrites the object.cache file used to access config data.
Please let me now if you able to resolve the issue.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Issue with Bulk Host Cloning and Import
It looks like we are still having errors when we verify the configs. Do we go ahead and restart Nagios Core, or do we need to fix the problematic config files prior to restarting?
Re: Issue with Bulk Host Cloning and Import
Nagios cannot start/restart with config errors. You would need to fix those errors before restarting nagios.
Did you remove the erroneous configs for the host/services, in the CCM PRIOR to running the steps below?
CCM -> Tools -> Config File Management
Delete Files
Write Configs
Verify Files
When you go to the CCM, you would see all of the "cloned" host/services as "Not Applied". Select these configs and delete them. Next, run the steps listed above. If there are no config errors, you can restart nagios.
Did you remove the erroneous configs for the host/services, in the CCM PRIOR to running the steps below?
CCM -> Tools -> Config File Management
Delete Files
Write Configs
Verify Files
When you go to the CCM, you would see all of the "cloned" host/services as "Not Applied". Select these configs and delete them. Next, run the steps listed above. If there are no config errors, you can restart nagios.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Issue with Bulk Host Cloning and Import
It looks like one of the previous administrators added config files in the backend manually instead of via the frontend. We noticed that the comments in the cfg files mention to "...import your configs into the CCM by placing them in the 'import' directory." We assume that if a file goes in here, then it should be ingested and overwrite any existing cfg files.
We've tried this a couple of times, but we haven't been able to get the good file that was manually created to overwrite the bad one that is generated when we click the "Write Configs" button. Can you tell us how we need to go about importing those config files?
We've tried this a couple of times, but we haven't been able to get the good file that was manually created to overwrite the bad one that is generated when we click the "Write Configs" button. Can you tell us how we need to go about importing those config files?
Re: Issue with Bulk Host Cloning and Import
Quick question, I am working with you on the ticket you opened, is it alright to close this post and continue exclusively in the ticket?
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Issue with Bulk Host Cloning and Import
Yes, that's good with me.