[dev.icinga.com #9242] Custom notification external commands do not work in a master-master setup

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/9242

Created by cwachinger on 2015-05-07 14:17:47 +00:00

Assignee: gbeutner
Status: Resolved (closed on 2016-06-07 10:50:06 +00:00)
Target Version: 2.5.0
Last Update: 2016-08-22 11:46:17 +00:00 (in Redmine)

Icinga Version: 2.3.4
Backport?: Not yet backported
Include in Changelog: 1

---

When sending a custom notification for a host/service to the master which is not currently responsible for notifications for this host/service the command is not relayed to the other master(s).

Changesets

2016-06-07 10:44:12 +00:00 by gbeutner 0eb0992

Fix custom notifications in a HA zone

fixes #9242

2016-06-13 08:48:59 +00:00 by gbeutner cb01f96

Don't forward SendNotifications messages to non-local zones

refs #9242

2016-06-13 09:13:25 +00:00 by gbeutner eb4aa44

Fix cluster permissions for SendNotifications messages

refs #9242

2016-06-14 05:57:52 +00:00 by gbeutner a8209c1

Change which instance is responsible for initiating notifications in a HA setup

refs #9242

---

Relations:

• duplicates #9242

[icinga-migration]

Updated by mj84 on 2015-09-09 09:08:29 +00:00

I am seeing a similar behaviour with Icinga 2.3.10, but in a master-slave setup.
Whenever i try to send a custom notification for a host being monitored through a satellite in icingaweb2, i can see that my master is receiving this external command:

[2015-09-09 11:00:33 +0200] information/ExternalCommandListener: Executing external command: [1441789070] SEND_CUSTOM_SVC_NOTIFICATION;satellite-host;load;3;admin;Test

My satellite is showing the following:
[2015-09-09 11:00:33 +0200] notice/ApiClient: Received 'event::SetForceNextNotification' message from 'master'
[2015-09-09 11:00:33 +0200] notice/ApiListener: Relaying 'event::SetForceNextNotification' message

The custom notification is never being executed by my satellite.
I would guess that my satellite is relaying the custom notification event back to my master (where i did not enable notifications due to bug #9437).

When i enable the notification feature on my master, my master is sending out the custom notification.
(Which is pretty much pointless, since i want to test notifications using a hardware umts dongle which is not present on the master.)

[icinga-migration]

Updated by aledermueller on 2015-10-27 10:19:27 +00:00

Same behavior like described by cwachinger in version v2.3.11-724-g2333015

[icinga-migration]

Updated by mfriedrich on 2016-04-07 12:10:39 +00:00

• Parent Id set to 11311

[icinga-migration]

Updated by mfriedrich on 2016-05-31 08:35:32 +00:00

#465861

[icinga-migration]

Updated by gbeutner on 2016-06-07 10:50:07 +00:00

• Status changed from New to Resolved
• Done % changed from 0 to 100

Applied in changeset 0eb0992.

[icinga-migration]

Updated by gbeutner on 2016-06-07 10:51:10 +00:00

• Assigned to set to gbeutner
• Target Version set to 2.5.0

[icinga-migration]

Updated by mfriedrich on 2016-06-16 06:36:00 +00:00

• Duplicated set to 11954

[icinga-migration]

Updated by mfriedrich on 2016-08-08 11:17:27 +00:00

• Parent Id deleted 11311

[icinga-migration]

Updated by gbeutner on 2016-08-22 11:46:17 +00:00

• Subject changed from Custom Notification External Commands do not work in a Master-Master setup to Custom notification external commands do not work in a master-master setup