###############################################################################
#
# Service configuration file
#
# Created by: Nagios Core Config Manager 2.6.0
# Date: 2016-10-20 11:49:31
# 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 {
host_name Device_1
use check_apc_pdu_alarms
register 1
}
###############################################################################
#
# Service configuration file
#
# END OF FILE
#
###############################################################################
This seems to happen on all multi-service files regardless of the type of service.
It seems you have 2 definitions of the same service. When imported, the first creates the service if it doesn't exist, and the second updates with info from the second definition. You can test by reversing the order and importing again. Having multiple services in one or more imported files doesn't seem to be a factor.
The validity of the service definitions is dependent on the templates, which aren't included.
gormank wrote:It seems you have 2 definitions of the same service. When imported, the first creates the service if it doesn't exist, and the second updates with info from the second definition. You can test by reversing the order and importing again. Having multiple services in one or more imported files doesn't seem to be a factor.
The validity of the service definitions is dependent on the templates, which aren't included.
Glad to hear it is resolved. I am going to lock the thread. Please feel free to post again if you have you another issue. Thank you for using the Nagios forums!