Configuration issues between master and satellite regarding notifications

Icinga 2
,
1

A little disclaimer first: this is the first time I’m messing around with satellites, so I wouldn’t rule out the possibility that I have configured something wrong.

I’m having an issue where my satellite can’t create its config as soon as there are notifications set up on the master instance. My current setup is one master and one satellite node. The node is located in a separate network from the master. Monitoring hosts within that separated network over the satellite works. However, when there are notifications setup on the master node, the satellite runs into an error when the new configuration is pushed to the satellite.

Output from the icinga2 log form the satellite atfer there is config with an notification (named it TEST) deployed on the master node (tail -f /var/log/icinga2/icinga2.log):
image

/var/lib/icinga2/api/zones-stage-startup-last-failed.log (repeats for every host that would be under the notification)

image
image1226×176 75.8 KB

(Log that goes beyond the screen, repeats also for every host)
critical/config: Error: Validation failed for object “HOST!TEST” of type ‘Notification’; Attribute ‘command’: Obejct ‘mail-host-notifcation’ of type ‘NotificationCommand’ does not exit

The master node is set up using the director; the satellite, on the other hand is only running icinga2 without anything else.
I have checked on the satellite that the scripts for host and service notification are present under /etc/icinga2/scripts.

2

Hi @Florian,
My guess is, that some part of the default configuration was removed/commented during the setup of the satellite machine.

So, two things here:

  • You could include the missing configuration (specifically /etc/icinga2/conf.d/commands.conf ) on the satellite, which will let the satellite accept the configuration. For this you can simply add the line include "conf.d/commands.conf" to /etc/icinga2/icinga2.conf. But …
  • In most setups only the central node(s) (“master(s)”) send notifications. If this is what you would like to do too, you can set the Zone of the Notifications to “master” (or “main” or whatever is that top level zone in your setup) and the Satellite will never even hear about them and be happy. Most likey you have to go to “Director” → “Notifications” → “Notification Templates” and set “Cluster Zone” (under “Zone Settings”) for the Templates there.
1 Like
3

I found my issue, thanks. In my notification template the zone was set to my satellite which caused the issue