Bulk modification tool not working

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Post Reply
kbauma01
Posts: 26
Joined: Wed May 25, 2022 6:39 am

Bulk modification tool not working

Post by kbauma01 »

I am trying to modify all hosts and services to have down and recovery for hosts, critical and recovery for services, using the bulk modification tool. I've tried it with a lot of servers and just one server and the setting is not being applied.

I go to CCM Bulk Modifications Tool --> Change and Single Config Option --> Choose Notifications options and check d and r under Hosts: and c and r under Services. Then I save the changes and Apply Configuration.

Is there a reason these settings are not saved? Do I need to restart something? Using Nagios XI 2024R1.
User avatar
jmichaelson
Posts: 117
Joined: Wed Aug 23, 2023 1:02 pm

Re: Bulk modification tool not working

Post by jmichaelson »

Since this is in CCM, are you clicking on the apply configuration button after you've made the changes? Nagios Core requires a restart after changes are made to its configuration, and clicking apply configuration in XI is how to ensure that happens.

Let me know if this helps.
Please let us know if you have any other questions or concerns.

-Jason
kbauma01
Posts: 26
Joined: Wed May 25, 2022 6:39 am

Re: Bulk modification tool not working

Post by kbauma01 »

I am clicking on the apply configuration button and that comes back as successful but nothing changes. When I tail -f /usr/local/nagiosxi/var/cmdsubsys.log

PROCESS COMMAND: CMD=17, DATA=
APPLYING NAGIOSCORE CONFIG...
CMDLINE=cd /usr/local/nagiosxi/scripts && ./reconfigure_nagios.sh

--- reset_config_perms.sh ------------
> Setting script permissions
> Setting CCM script permissions
> Setting special script permissions
> Setting special component script permissions
> Setting migrate permissions
> Setting configuration file/directory permissions
> Setting perfdata directory and RRD permissions
...> Setting libexec directory permissions
> Setting Nagios XI config permissions
> Setting NOM checkpoint user:group permissions
> + Setting Nagios Core corelog.newobjects user:group permissions
> + Setting Recurring Downtime file user:group permissions
> + Setting BPI configuration file user:group permissions
--------------------------------------

--- ccm_import.php -------------------
> Setting import directory: /usr/local/nagios/etc/import/
> Importing config files into the CCM
No files to import
--------------------------------------
.
--- ccm_export.php -------------------
> Writing CCM configuration to Nagios files
..... Finished writing out configuraton
--------------------------------------
.................
--------------------------------------
> Verifying configuration with Nagios Core
> Output:
Nagios Core 4.4.13
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 2023-06-01
License: GPL

Website: https://www.nagios.org
Reading configuration data...
Read main config file okay...
Checked 19299 services.
Checked 1422 hosts.
Checked 51 host groups.
Checked 69 service groups.
Checked 165 contacts.
Checked 66 contact groups.
Checked 268 commands.
Checked 19 time periods.
Checked 0 host escalations.
Checked 0 service escalations.
Checking for circular paths...
Checked 1422 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 19 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 0
Total Errors: 0

Things look okay - No serious problems were detected during the pre-flight check
> Return Code: 0
--------------------------------------
......OUTPUT=--------------------------------------
RETURNCODE=0
gwesterman
Posts: 97
Joined: Wed Aug 23, 2023 11:29 am

Re: Bulk modification tool not working

Post by gwesterman »

Hi @kbauma01,

After playing around with the tool a bit, I found that this particular bulk modification option only appears to successfully apply if you select only one of the available options for each of the hosts and services selected (e.g. only d for the hosts selected and/or only w for the services selected). This is most likely a bug and will be noted.

Thank you!
Post Reply