maybe chmod 0644 'icinga2/conf.d/users.conf'
maybe chown 'nagios' 'icinga2/constants.conf'
maybe chgrp 'nagios' 'icinga2/constants.conf'
-maybe chmod 0640 'icinga2/constants.conf'
+maybe chmod 0644 'icinga2/constants.conf'
+maybe chown 'nagios' 'icinga2/constants.conf.orig'
+maybe chgrp 'nagios' 'icinga2/constants.conf.orig'
+maybe chmod 0640 'icinga2/constants.conf.orig'
maybe chown 'nagios' 'icinga2/features-available'
maybe chgrp 'nagios' 'icinga2/features-available'
maybe chmod 0750 'icinga2/features-available'
maybe chown 'nagios' 'icinga2/features-available/api.conf'
maybe chgrp 'nagios' 'icinga2/features-available/api.conf'
maybe chmod 0644 'icinga2/features-available/api.conf'
+maybe chown 'nagios' 'icinga2/features-available/api.conf.orig'
+maybe chgrp 'nagios' 'icinga2/features-available/api.conf.orig'
+maybe chmod 0644 'icinga2/features-available/api.conf.orig'
maybe chown 'nagios' 'icinga2/features-available/checker.conf'
maybe chgrp 'nagios' 'icinga2/features-available/checker.conf'
maybe chmod 0644 'icinga2/features-available/checker.conf'
maybe chmod 0750 'icinga2/features-enabled'
maybe chown 'nagios' 'icinga2/icinga2.conf'
maybe chgrp 'nagios' 'icinga2/icinga2.conf'
-maybe chmod 0640 'icinga2/icinga2.conf'
+maybe chmod 0644 'icinga2/icinga2.conf'
+maybe chown 'nagios' 'icinga2/icinga2.conf.orig'
+maybe chgrp 'nagios' 'icinga2/icinga2.conf.orig'
+maybe chmod 0640 'icinga2/icinga2.conf.orig'
maybe chown 'nagios' 'icinga2/pki'
maybe chgrp 'nagios' 'icinga2/pki'
maybe chmod 0700 'icinga2/pki'
maybe chmod 0755 'icinga2/scripts/mail-service-notification.sh'
maybe chown 'nagios' 'icinga2/zones.conf'
maybe chgrp 'nagios' 'icinga2/zones.conf'
-maybe chmod 0640 'icinga2/zones.conf'
+maybe chmod 0644 'icinga2/zones.conf'
+maybe chown 'nagios' 'icinga2/zones.conf.orig'
+maybe chgrp 'nagios' 'icinga2/zones.conf.orig'
+maybe chmod 0640 'icinga2/zones.conf.orig'
maybe chown 'nagios' 'icinga2/zones.d'
maybe chgrp 'nagios' 'icinga2/zones.d'
maybe chmod 0750 'icinga2/zones.d'
/* Our local instance name. By default this is the server's hostname as returned by `hostname --fqdn`.
* This should be the common name from the API certificate.
*/
-//const NodeName = "localhost"
+const NodeName = "vserver2.hoellein.online"
/* Our local zone name. */
-const ZoneName = NodeName
+const ZoneName = "vserver2.hoellein.online"
/* Secret key for remote node tickets */
const TicketSalt = ""
--- /dev/null
+/**
+ * This file defines global constants which can be used in
+ * the other configuration files.
+ */
+
+/* The directory which contains the plugins from the Monitoring Plugins project. */
+const PluginDir = "/usr/lib/nagios/plugins"
+
+/* The directory which contains the Manubulon plugins.
+ * Check the documentation, chapter "SNMP Manubulon Plugin Check Commands", for details.
+ */
+const ManubulonPluginDir = "/usr/lib/nagios/plugins"
+
+/* The directory which you use to store additional plugins which ITL provides user contributed command definitions for.
+ * Check the documentation, chapter "Plugins Contribution", for details.
+ */
+const PluginContribDir = "/usr/lib/nagios/plugins"
+
+/* Our local instance name. By default this is the server's hostname as returned by `hostname --fqdn`.
+ * This should be the common name from the API certificate.
+ */
+//const NodeName = "localhost"
+
+/* Our local zone name. */
+const ZoneName = NodeName
+
+/* Secret key for remote node tickets */
+const TicketSalt = ""
/**
* The API listener is used for distributed monitoring setups.
*/
-
object ApiListener "api" {
- //accept_config = false
- //accept_commands = false
-
- ticket_salt = TicketSalt
+ accept_config = true
+ accept_commands = true
+ bind_host = "icinga.hoellein.online"
}
--- /dev/null
+/**
+ * The API listener is used for distributed monitoring setups.
+ */
+
+object ApiListener "api" {
+ //accept_config = false
+ //accept_commands = false
+
+ ticket_salt = TicketSalt
+}
--- /dev/null
+../features-available/api.conf
\ No newline at end of file
+++ /dev/null
-../features-available/notification.conf
\ No newline at end of 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".
*/
-include_recursive "conf.d"
+// Disabled by the node setup CLI command on 2023-05-26 11:47:29 +0200
+// Disabled by the node setup CLI command on 2023-05-26 11:54:18 +0200
+// Disabled by the node setup CLI command on 2023-05-26 11:57:21 +0200
+// include_recursive "conf.d"
--- /dev/null
+/**
+ * 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".
+ */
+include_recursive "conf.d"
/*
- * Endpoint and Zone configuration for a cluster setup
- * This local example requires `NodeName` defined in
- * constants.conf.
+ * Generated by Icinga 2 node setup commands
+ * on 2023-05-26 11:57:18 +0200
*/
-object Endpoint NodeName {
- host = NodeName
+object Endpoint "mail.hoellein.online" {
+ host = "icinga.hoellein.online"
+ port = "5665"
}
-object Zone ZoneName {
- endpoints = [ NodeName ]
+object Zone "mail.hoellein.online" {
+ endpoints = [ "mail.hoellein.online" ]
}
-/*
- * 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
+object Endpoint "vserver2.hoellein.online" {
}
-/*
- * 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
+object Zone "vserver2.hoellein.online" {
+ endpoints = [ "vserver2.hoellein.online" ]
+ parent = "mail.hoellein.online"
}
-/*
- * Read the documentation on how to configure
- * a cluster setup with multiple zones.
- */
-
-/*
-object Endpoint "master.example.org" {
- host = "master.example.org"
-}
-
-object Endpoint "satellite.example.org" {
- host = "satellite.example.org"
+object Zone "global-templates" {
+ global = true
}
-object Zone "master" {
- endpoints = [ "master.example.org" ]
+object Zone "director-global" {
+ global = true
}
-object Zone "satellite" {
- parent = "master"
- endpoints = [ "satellite.example.org" ]
-}
-*/
--- /dev/null
+/*
+ * Endpoint and Zone configuration for a cluster setup
+ * This local example requires `NodeName` defined in
+ * constants.conf.
+ */
+
+object Endpoint NodeName {
+ host = NodeName
+}
+
+object Zone ZoneName {
+ endpoints = [ NodeName ]
+}
+
+/*
+ * 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
+}
+
+/*
+ * Read the documentation on how to configure
+ * a cluster setup with multiple zones.
+ */
+
+/*
+object Endpoint "master.example.org" {
+ host = "master.example.org"
+}
+
+object Endpoint "satellite.example.org" {
+ host = "satellite.example.org"
+}
+
+object Zone "master" {
+ endpoints = [ "master.example.org" ]
+}
+
+object Zone "satellite" {
+ parent = "master"
+ endpoints = [ "satellite.example.org" ]
+}
+*/
+
projects / vserver2 / commitdiff