Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dev.icinga.com #10505] Acknowledgment not displayed if the service was ack'ed on other cluster member #2115

Closed
icinga-migration opened this issue Oct 31, 2015 · 13 comments
Assignees
Labels
area/monitoring Affects the monitoring module bug Something isn't working queue/important Blocks a release or needs immediate attention

Comments

@icinga-migration
Copy link

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

Created by tobiasvdk on 2015-10-31 13:04:37 +00:00

Assignee: elippmann
Status: Assigned
Target Version: Backlog
Last Update: 2016-02-17 16:47:24 +00:00 (in Redmine)


I have a distributed icinga 2 setup with one master and some slaves. If I acknowledge a service on the master, the acknowledgement is shown fine in the master's webui but on the slave I get the error (and vice versa):

Fatal error: Call to a member function getAuthor() on null in zend.view:///usr/share/icingaweb2/modules/monitoring/application/views/scripts/show/components/acknowledgement.phtml on line 20

screenshot:
icingaweb2_ack_problem.png

The database seems to be fine:

master:

icinga2idopgsql=> select * from icinga_acknowledgements where comment_data like 'ack on %';
 acknowledgement_id | instance_id |       entry_time       | entry_time_usec | acknowledgement_type | object_id | state | author_name  | comment_data  | is_sticky | persistent_comment | notify_contacts |        end_time        | endpoint_object_id 
--------------------+-------------+------------------------+-----------------+----------------------+-----------+-------+--------------+---------------+-----------+--------------------+-----------------+------------------------+--------------------
                  4 |           1 | 2015-10-31 12:10:35+00 |          255068 |                    2 |       508 |     1 | tvonderkrone | ack on master |         1 |                  1 |               1 | 2015-10-31 14:10:21+00 |                  3
                  5 |           1 | 2015-10-31 12:11:13+00 |          207911 |                    2 |       510 |     1 | tvonderkrone | ack on slave  |         1 |                  1 |               1 | 2015-10-31 14:11:01+00 |                  3
(2 rows)

slave:

icinga2idopgsql=> select * from icinga_acknowledgements where comment_data like 'ack on %';
 acknowledgement_id | instance_id |       entry_time       | entry_time_usec | acknowledgement_type | object_id | state | author_name  | comment_data  | is_sticky | persistent_comment | notify_contacts |        end_time        | endpoint_object_id 
--------------------+-------------+------------------------+-----------------+----------------------+-----------+-------+--------------+---------------+-----------+--------------------+-----------------+------------------------+--------------------
                  4 |           1 | 2015-10-31 12:10:35+00 |          267328 |                    2 |       495 |     1 | tvonderkrone | ack on master |         1 |                  1 |               1 | 2015-10-31 14:10:21+00 |                  1
                  5 |           1 | 2015-10-31 12:11:13+00 |          189793 |                    2 |       497 |     1 | tvonderkrone | ack on slave  |         1 |                  1 |               1 | 2015-10-31 14:11:01+00 |                  1
(2 rows)

My setup:

  • debian jessie
  • postgresql 9.4
  • icinga 2.4 commit 1b9f0a8c77b3c00f87f9ee0e9515098c7b0ab4fb
  • icingaweb2 commit 5db8d08

Attachments

Changesets

2015-11-16 13:35:48 +00:00 by elippmann ba62753

monitoring: Fix exception if the comment of an acknowledgement is missing

refs #10505

Relations:

@icinga-migration
Copy link
Author

Updated by JamesForman on 2015-11-12 03:29:40 +00:00

We are also experiencing this issue with our Icinga2 setup.

The error (identical to the message in the main post) appears on both Icinga2 servers, however this may be because the IDO-MySQL feature on each server has "enable_ha = false" set

Our setup:

  • Ubuntu 14.04
  • MySQL 14.14 Distrib 5.5.46
  • Icinga2 v2.3.10 (from official package)
  • IcingaWeb2 v2.0.0 (from official package)

@icinga-migration
Copy link
Author

Updated by icinga-kanban on 2015-11-16 13:39:42 +00:00

Build !#1146 triggered by the commits ba62753, 338804c passed successfully.

Branch: origin/master
Author: Eric Lippmann

@icinga-migration
Copy link
Author

Updated by tobiasvdk on 2015-11-18 14:59:48 +00:00

As you can see in the description the comment_data is on both, the master and the slave/satellite.

@icinga-migration
Copy link
Author

Updated by aklimov on 2015-12-16 10:59:30 +00:00

  • Status changed from New to Feedback
  • Assigned to set to tobiasvdk

Hi tobiasvdk,

This should have been fixed in IW2 ba62753. Please test again with v2.1.

Best,
Alex

@icinga-migration
Copy link
Author

Updated by tobiasvdk on 2015-12-17 14:59:59 +00:00

  • File added ack2.png
  • File added ack1.png

The error message is gone but it doesn't work as expected. Since the database entries are on both servers it should display the same information on both hosts, shouldn't it?
Server were I ack'ed the alarm:
ack1.png

Satellite:
ack2.png

The 'x' shows that the ack is recognized but there is no information about who ack'ed the host with what comment.

@icinga-migration
Copy link
Author

Updated by tobiasvdk on 2016-01-13 09:57:11 +00:00

  • Assigned to changed from tobiasvdk to aklimov

Assigning back because issue is not resolved completely yet.

@icinga-migration
Copy link
Author

Updated by aklimov on 2016-01-21 16:54:22 +00:00

Hi tobiasvdk,

This is likely to be an Icinga 2 error. Please try the latest stable 2.4.x and tell whether it's still not working.

Best,
Alex

@icinga-migration
Copy link
Author

Updated by aklimov on 2016-01-21 16:54:42 +00:00

  • Assigned to changed from aklimov to tobiasvdk

@icinga-migration
Copy link
Author

Updated by tobiasvdk on 2016-01-26 07:52:13 +00:00

The same error with icinga 2 2.4.1:

$ sudo icinga2 --version
icinga2 - The Icinga 2 network monitoring daemon (version: r2.4.1-1)

Copyright (c) 2012-2015 Icinga Development Team (https://www.icinga.org)
License GPLv2+: GNU GPL version 2 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Application information:
  Installation root: /usr
  Sysconf directory: /etc
  Run directory: /run
  Local state directory: /var
  Package data directory: /usr/share/icinga2
  State path: /var/lib/icinga2/icinga2.state
  Modified attributes path: /var/lib/icinga2/modified-attributes.conf
  Objects path: /var/cache/icinga2/icinga2.debug
  Vars path: /var/cache/icinga2/icinga2.vars
  PID path: /run/icinga2/icinga2.pid

System information:
  Platform: Debian GNU/Linux
  Platform version: "8 (jessie)
  Kernel: Linux
  Kernel version: 4.3.0-0.bpo.1-amd64
  Architecture: x86_64

The database shows the correct "comment_data". What query does icingaweb2 run?

@icinga-migration
Copy link
Author

Updated by tobiasvdk on 2016-02-16 11:02:57 +00:00

  • Relates set to 10733

@icinga-migration
Copy link
Author

Updated by elippmann on 2016-02-17 16:46:21 +00:00

  • Category set to Monitoring
  • Status changed from Feedback to Assigned
  • Assigned to changed from tobiasvdk to elippmann

Hi,

As you've already discovered, this is an Icinga 2 bug. I try to get more information.

Best,
Eric

@icinga-migration
Copy link
Author

Updated by elippmann on 2016-02-17 16:47:24 +00:00

  • Priority changed from Normal to High
  • Target Version set to Backlog

@icinga-migration icinga-migration added queue/important Blocks a release or needs immediate attention bug Something isn't working area/monitoring Affects the monitoring module labels Jan 17, 2017
@icinga-migration icinga-migration added this to the Backlog milestone Jan 17, 2017
@lippserd
Copy link
Member

lippserd commented Jul 5, 2017

Should be fixed. If not, please open a new issue.

@lippserd lippserd closed this as completed Jul 5, 2017
@lippserd lippserd removed this from the Backlog milestone Sep 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/monitoring Affects the monitoring module bug Something isn't working queue/important Blocks a release or needs immediate attention
Projects
None yet
Development

No branches or pull requests

2 participants