[dev.icinga.com #9106] Icinga no longer sending acknowledgement notifications #1551
Comments
Updated by mfriedrich on 2015-04-20 09:18:38 +00:00
Please post the external command being logged. |
Updated by ziesemer on 2015-04-20 12:08:45 +00:00 Are you looking for the external command of the acknowledgement action? Here is a sanitized (host and service description) log snippet:
(I will work on also reproducing with a sample configuration so that we don't need to be concerned with sanitizing outputs here.) |
Updated by ziesemer on 2015-04-29 02:11:00 +00:00
Sorry for the delay.
I acknowledged the critical service. The debugging log is attached in attachment:Ack-1.12.2.txt. Everything looks exactly as expected. I then shutdown, upgraded to 1.13.2 - replacing everything but the "etc" and "var" folders to keep the same configuration. Also removed the "objects.cache" and "retention.dat" from "var" - clearing out my acknowledgement in the process. Restarted with 1.13.2, and re-acknowledged the critical service. The debugging log is attached in attachment:NoAck-1.13.2.txt. Note how much smaller it is - and again, it skips the "Making callbacks (type 29)..." and everything that follows, and again skips to "Making callbacks (type 24)..." and everything related to the notification in-between. |
Updated by mfriedrich on 2015-04-29 17:21:37 +00:00
http://docs.icinga.org/latest/en/extcommands2.html
notify=0 |
Updated by mfriedrich on 2015-04-29 17:29:32 +00:00
I've pushed 4a40a06 to the git master which probably fixes your problem. Please test that patch and report back. |
Updated by ziesemer on 2015-04-29 19:42:31 +00:00 Sorry - didn't seem to have helped:
I downloaded https://github.com/Icinga/icinga-core/archive/master.zip , verified the referenced changes were in my I repeated the test after running:
... just to validate that I was using the latest code, as this became visible on the UI and in the logs:
... and still experienced the same results. No notifications, or all the extra related debugging concerning them. |
Updated by mfriedrich on 2015-04-30 20:39:20 +00:00
Mh ok, think I've found it. Ticking off the checkbox (no notifications)
Enabling it
Please test the pushed fix to git master. |
Updated by ziesemer on 2015-05-01 01:16:37 +00:00 Working much better now, thank you! (Will eagerly await the 1.13.3 release.) |
Updated by mfriedrich on 2015-05-01 10:53:29 +00:00
Ok thanks for your patience :) Let's see how long it takes for the next bugfix release. |
Updated by mfriedrich on 2015-05-01 10:53:59 +00:00
|
Updated by mfriedrich on 2015-05-01 10:54:10 +00:00
|
Updated by mfriedrich on 2015-06-09 17:28:22 +00:00
|
Updated by mfriedrich on 2015-07-15 09:41:36 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/9106
Created by ziesemer on 2015-04-17 16:46:46 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2015-05-01 10:53:59 +00:00)
Target Version: 1.13.3
Last Update: 2015-07-15 09:41:36 +00:00 (in Redmine)
After upgrading from 1.12.2 to 1.13.2, acknowledgements are taking effect - but no longer sending the notifications concerning them. Other notifications (problem, custom, recovery) continue to work as expected.
The ACK shows in the event log, but not in the notification log.
Running with full debug logging: In 1.12.2, immediately after "Making callbacks (type 29)..." is a "service_notification()" call - followed by many lines related to sending the notification, followed by schedule_new_event(). In 1.13.2, service_notification() is skipped, and everything jumps directly to schedule_new_event(). Reverting to 1.12.2 - keeping the same configurations - resumes proper functionality.
This is reproducible on multiple servers - each running builds from source.
Attachments
Changesets
2015-04-29 17:27:42 +00:00 by (unknown) 4a40a06
2015-04-30 20:38:32 +00:00 by mfriedrich 9c47932
Relations:
The text was updated successfully, but these errors were encountered: