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 #7731] Reminder notifications not being sent but logged every 5 secs #2274

Closed
icinga-migration opened this issue Nov 19, 2014 · 11 comments
Labels
area/notifications Notification events bug Something isn't working
Milestone

Comments

@icinga-migration
Copy link

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

Created by agherardi on 2014-11-19 04:56:12 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2015-02-12 13:55:03 +00:00)
Target Version: 2.3.0
Last Update: 2015-02-12 13:55:03 +00:00 (in Redmine)

Icinga Version: 2.1.0-1

I see hundreds of entries like this in /var/log/icinga2/icinga2.log:

[2014-11-18 16:03:53 -0800] information/NotificationComponent: Sending reminder notification for object 'TARDISXXXCORE05!Mongo Replication Lag'

All entries are for the same object - same host, same service.

I'm attaching my configuration.

Attachments

Changesets

2015-02-12 13:51:17 +00:00 by (unknown) 8c8e80b

Don't spam the log with reminder notifications not being sent

fixes #7731

Relations:

@icinga-migration
Copy link
Author

Updated by agherardi on 2014-11-19 21:00:56 +00:00

OK, I think I know what's going on.

I have a notification filter state set to [OK, Critical]. The replication lag is a warning, so a notification is never sent and SetLastProblemNotification() is never called.

The condition:

if (notification~~GetInterval() <= 0 && notification~~>GetLastProblemNotification() > checkable->GetLastHardStateChange())

in NotificationComponent::NotificationTimerHandler(void) is always false and the "Sending reminder notification" message keeps getting logged every time the timer fires - i.e., every 5 seconds - even though no notification is actually sent.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2014-11-24 11:54:21 +00:00

  • Target Version set to 2.3.0

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-01-08 15:28:24 +00:00

  • Relates set to 8063

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-01-26 15:05:59 +00:00

  • Target Version changed from 2.3.0 to 2.4.0

@icinga-migration
Copy link
Author

Updated by deneu on 2015-01-28 12:12:50 +00:00

same issue in my setup?

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-02-09 09:28:29 +00:00

  • Status changed from New to Assigned
  • Assigned to set to mfriedrich
  • Target Version changed from 2.4.0 to 2.3.0

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-02-09 12:17:49 +00:00

  • Priority changed from Normal to Low

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-02-09 12:21:31 +00:00

  • Estimated Hours set to 2

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-02-12 13:33:20 +00:00

The problem is that this log entry is added before the notification filters are checked. Which could prevent sending a notification.

We should move that entry into 'notice', and rename it a bit. Notification being sent successfully is still logged with 'information' level.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-02-12 13:53:27 +00:00

  • Subject changed from Icinga2 keeps sending reminder notification every 5 seconds to Reminder notifications not being sent but logged every 5 secs

@icinga-migration
Copy link
Author

Updated by Anonymous on 2015-02-12 13:55:03 +00:00

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

Applied in changeset 8c8e80b.

@icinga-migration icinga-migration added Low bug Something isn't working area/notifications Notification events labels Jan 17, 2017
@icinga-migration icinga-migration added this to the 2.3.0 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/notifications Notification events bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant