First, some facts:
[root@nagios ~]# cat /etc/redhat-release
CentOS Linux release 7.3.1611 (Core)
This is an installation and not the pre-built image, x64, with nothing else special or installed.
After the upgrade we had a couple issues, a handful of hosts lost their max_check_attempts for no apparent reason and several host and service templates originating (and named) xi* had to be deactivated (but were unused anyways). Basically, some weird behavior.
We did do an upgrade and then rolled back, but we did so using snapshots on the whole VM so I doubt that caused any issues.
Here is an example:
Using username "root".
Last login: Thu Mar 16 08:20:10 2017 from buffalo-jdix.provident.local
[root@nagios ~]# cat /usr/local/nagios/etc/services/testingService.cfg
###############################################################################
#
# Service configuration file
#
# Created by: Nagios Core Config Manager 2.6.5
# Date: 2017-03-16 13:48:53
# Version: Nagios 3.x config file
#
# --- DO NOT EDIT THIS FILE BY HAND ---
# Nagios CCM will overwrite all manual settings during the next update if you
# would like to edit files manually, place them in the 'static' directory or
# import your configs into the CCM by placing them in the 'import' directory.
#
###############################################################################
define service {
service_description testing a service
check_command check-fast-alive!!!!!!!!
register 1
}
###############################################################################
#
# Service configuration file
#
# END OF FILE
#
###############################################################################
[root@nagios ~]#
As a workaround I recreated the problem services in the static config directory.
Thoughts?
I also uploaded my update logs as an attachment. (redacted as it contained host names)
. The attachment I removed because it contains data I don't want to post publicly. Is there a way to get this to support without sharing it with the world?