Hello,
Im currently facing a issue with a new icinga Installation.
I have setup everything succesfull and im trying to monitor now some special Services for a host.
When I apply a Service to a host with arguments like
apply Service "XY" {
import "generic-service"
}
Im getting an error, that he doesnt know the “generic-service” Template?
I have never seen this error before.
Logs dont say more Information as
critical/config: Error: Import references unknown template: 'generic-service'
In the default zones.conf File it says something to the gloabl/direcor-templates:
/*
* Defines a global zone for distributed setups with masters,
* satellites and clients.
* This is required to sync configuration commands,
* templates, apply rules, etc. to satellite and clients.
* All nodes require the same configuration and must
* have `accept_config` enabled in the `api` feature.
*/
object Zone "global-templates" {
global = true
}
/*
* Defines a global zone for the Icinga Director.
* This is required to sync configuration commands,
* templates, apply rules, etc. to satellite and clients.
* All nodes require the same configuration and must
* have `accept_config` enabled in the `api` feature.
*/
object Zone "director-global" {
global = true
}
My icinga2-conf looks like:
/**
* Icinga 2 configuration file
* - this is where you define settings for the Icinga application including
* which hosts/services to check.
*
* For an overview of all available configuration options please refer
* to the documentation that is distributed as part of Icinga 2.
*/
/**
* The constants.conf defines global constants.
*/
include "constants.conf"
/**
* The zones.conf defines zones for a cluster setup.
* Not required for single instance setups.
*/
include "zones.conf"
/**
* The Icinga Template Library (ITL) provides a number of useful templates
* and command definitions.
* Common monitoring plugin command definitions are included separately.
*/
include <itl>
include <plugins>
include <plugins-contrib>
include <manubulon>
/**
* This includes the Icinga 2 Windows plugins. These command definitions
* are required on a master node when a client is used as command endpoint.
*/
include <windows-plugins>
/**
* This includes the NSClient++ check commands. These command definitions
* are required on a master node when a client is used as command endpoint.
*/
include <nscp>
/**
* The features-available directory contains a number of configuration
* files for features which can be enabled and disabled using the
* icinga2 feature enable / icinga2 feature disable CLI commands.
* These commands work by creating and removing symbolic links in
* the features-enabled directory.
*/
include "features-enabled/*.conf"
/**
* Although in theory you could define all your objects in this file
* the preferred way is to create separate directories and files in the conf.d
* directory. Each of these files must have the file extension ".conf".
*/
// Disabled by the node setup CLI command on 2023-09-26 11:35:39 +0000
// Disabled by the node setup CLI command on 2023-09-27 06:52:57 +0000
// include_recursive "conf.d"
// Added by the node setup CLI command on 2023-09-26 11:35:39 +0000
include "conf.d/api-users.conf"
Can anyone support on this?