Unable to apply config even after removing problem configs

[uidaho]

We would like to have Nagios Support look at a problem with applying a config to our Nagios XI 5.7.3 instance.

When attempting to "Apply Config" within Core Config Manager, we receive these errors:

Error: Invalid max_attempts, check_interval, retry_interval, or notification_interval value for service 'Status of 9200' on host 'seclogger01'
Error: Could not register service (config file '/usr/local/nagios/etc/services/Humio_9200.cfg', starting on line 16)

This occurs even after removing the hosts and services mentioned, confirmed both in CCM and on the file system.

We are also unable to revert to a couple of recent config snapshots, all with the same error.

[benjaminsmith]

Hi,

Let's try to de-activate that service and they run through the following process. Go to Configure > CCM > Tools > Config File Management

1. Delete Files
2. Write Files
3. Verify Files ( If you see any errors follow the message to correct and repeat steps 1-3 until it passes)
4. Restart Nagios Core

Once you're able to get a clean verification and restart, then try to re-activate the service and then correct the Invalid max_attempts, check_interval, retry_interval, or notification_interval settings for the service.

Let me know if you're able to resolve the issue.

Benjamin

[uidaho]

Nagios support found our problem. The files in the output were not where the problem was (evident by the fact the files did not exist but still showed in the error when applying config failed).

They found two incomplete config files in the directory
/usr/local/nagios/etc/import/

Once these were moved, the support technician ran the script
/usr/local/nagiosxi/scripts/reconfigure_nagios.sh
and then was able to apply configuration without error.

I don't really understand how these got here, but it has something to do with creating a monitor with XI.

[cdienger]

Thanks for the update. The process of applying configuration includes writing files to this directory so it is possible something may have been left behind if there was a problem applying the configuration at some point.