Hello,
We are running NagiosXI 5.4.7. When trying to add services to a new host using the bulk modification tool, it seems like if I choose more than 3 services at a time, I get a failure when applying the config. I can do one or two services and it works, for the most part, but not always guaranteed.
Any thoughts?
Thanks,
Alex
Bulk modification tool apply config errors
-
gsl_ops_practice
- Posts: 151
- Joined: Thu Apr 09, 2015 9:14 pm
Re: Bulk modification tool apply config errors
What are the exact configuration errors that you see? As of now, you can only add valid service configs, where object variables are defined on a "service" level, not inherited from a template.
Under the Bulk Modifications Tool page (Add Service(s) to Hosts), it says:
Under the Bulk Modifications Tool page (Add Service(s) to Hosts), it says:
It should probably say:** Parent, contact, and group relationships will not be copied **
as templates don't seem to be inherited. This has been overlooked. We will be changing this message in the next release.** Parent, contact, group, and template relationships will not be copied **
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
gsl_ops_practice
- Posts: 151
- Joined: Thu Apr 09, 2015 9:14 pm
Re: Bulk modification tool apply config errors
1. I have a host with configured monitors, all is well.
2. I duplicate that host a couple of times since I have 3 cluster members doing the same work
3. Using the bulk modification tool, use "Add services" to add monitors from the first host to the other 2 and get this error:
An error occurred while attempting to apply your configuration to Nagios Core. Monitoring engine configuration files have been rolled back to their last known good checkpoint.
Error: Service description, host name, or check command is NULL
Error: Could not register service (config file '/usr/local/nagios/etc/services/new_host_2.cfg', starting on line 212)
The host check command is not null, which is why this is confusing.
2. I duplicate that host a couple of times since I have 3 cluster members doing the same work
3. Using the bulk modification tool, use "Add services" to add monitors from the first host to the other 2 and get this error:
An error occurred while attempting to apply your configuration to Nagios Core. Monitoring engine configuration files have been rolled back to their last known good checkpoint.
Error: Service description, host name, or check command is NULL
Error: Could not register service (config file '/usr/local/nagios/etc/services/new_host_2.cfg', starting on line 212)
The host check command is not null, which is why this is confusing.
Re: Bulk modification tool apply config errors
We were able to recreate the issue in-house, and filed an internal bug report (task_id=13585). The problem is that the host template doesn't get transferred from the original host to the "clones". The check command is NULL, and apply configuration fails. We will be fixing the issue as soon as we can, but for the time being I would recommend that you use Bulk Host Cloning and Import wizard instead.
https://assets.nagios.com/downloads/nag ... Wizard.pdf
https://assets.nagios.com/downloads/nag ... Wizard.pdf
Be sure to check out our Knowledgebase for helpful articles and solutions!
Re: Bulk modification tool apply config errors
After looking into this, it is not a bug. It does not copy the service templates that are applied to the added services. You should be able to go to the service in the CCM, click the download icon for any of the services with the config name new_host_2 and open it in an editor with lines and find line 219 which is going to be a service definition missing some values.
If you copy things like the generic Ping service that is on most hosts generated from config wizards, the check_command is defined in the service template, which is not copied over.
I've updated the text above the box to include that templates are not copied over. We will also look into improving this feature in future versions so that it can copy over services with more complex setups easier.
If you copy things like the generic Ping service that is on most hosts generated from config wizards, the check_command is defined in the service template, which is not copied over.
I've updated the text above the box to include that templates are not copied over. We will also look into improving this feature in future versions so that it can copy over services with more complex setups easier.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.