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 #9997] "icinga" check should have state WARNING when the last reload failed #3321

Closed
icinga-migration opened this issue Aug 26, 2015 · 16 comments

Comments

Projects
None yet
1 participant
@icinga-migration
Copy link
Member

commented Aug 26, 2015

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

Created by lbetz on 2015-08-26 08:29:47 +00:00

Assignee: gbeutner
Status: Resolved (closed on 2016-05-11 14:10:04 +00:00)
Target Version: 2.4.8
Last Update: 2016-05-11 14:10:04 +00:00 (in Redmine)

Backport?: Not yet backported
Include in Changelog: 1

If you have many agent/satellites in your setup and there is a configuration problem on some agents/satellites the reload failed. How I notice this? Maybe it's possible to add anything to the icinga plugin that inform the user with a warning?

Attachments

Changesets

2016-05-11 14:07:28 +00:00 by gbeutner 1ad4d9c

Report failed reload attempts for the icinga check

fixes #9060
fixes #9997
fixes #11129

2016-05-12 09:11:03 +00:00 by gbeutner ff24863

Report failed reload attempts for the icinga check

fixes #9060
fixes #9997
fixes #11129

Relations:

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Aug 26, 2015

Updated by seferovic on 2015-08-26 09:10:55 +00:00

Wouldn't you see that the zone is disconnected on the master? Or you could check the agent port on the remote machine?

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Aug 26, 2015

Updated by lbetz on 2015-08-26 12:08:58 +00:00

The zone is still connected and icings is running. But the reload failed because you've a corrupt configuration, i.e. duplicate definitions. At this time the only chance to detect this, is to look into the log file. But it's important to know, if your new configuration isn't active on satellites or agents.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Aug 27, 2015

Updated by mfriedrich on 2015-08-27 14:27:37 +00:00

  • Relates set to 10013
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Aug 31, 2015

Updated by mfriedrich on 2015-08-31 15:13:27 +00:00

  • Category set to libicinga
  • Status changed from New to Feedback
  • Assigned to set to lbetz

The question is rather - what would trigger a warning? last failed config validation within amount of time X (threshold)?

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Aug 31, 2015

Updated by lbetz on 2015-08-31 20:25:58 +00:00

  • File added signature.asc

Icinga got a reload from i.e. the master instance, the validation failed and a warning thru the cluster-zone check would be fine, immediately I think.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Sep 5, 2015

Updated by mfriedrich on 2015-09-05 11:01:03 +00:00

  • Subject changed from Give notice if a reload of icinga failed to Notify the master if a cluster node's reload failed
  • Status changed from Feedback to New
  • Assigned to deleted lbetz

There's a problem with our cluster protocol only sending asynchronous notifications (e.g. sending a config update and waiting for an answer is not possible at this point). Not sure how satellites would be able to notify their (reload) state back to parent instances.

I totally understand the idea, but currently I don't have a good design in mind. Will discuss this with Gunnar when he's back.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Sep 5, 2015

Updated by mfriedrich on 2015-09-05 11:01:13 +00:00

  • Status changed from New to Assigned
  • Assigned to set to mfriedrich
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Nov 14, 2015

Updated by gbeutner on 2015-11-14 18:45:24 +00:00

  • Subject changed from Notify the master if a cluster node's reload failed to "icinga" check should have state WARNING when the last reload failed
  • Category changed from libicinga to libmethods
  • Assigned to deleted mfriedrich
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Nov 14, 2015

Updated by gbeutner on 2015-11-14 18:45:29 +00:00

  • Status changed from Assigned to New
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jan 22, 2016

Updated by mfriedrich on 2016-01-22 14:56:43 +00:00

  • Target Version set to Backlog
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Feb 24, 2016

Updated by mfriedrich on 2016-02-24 23:32:07 +00:00

  • Relates set to 11129
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Feb 24, 2016

Updated by mfriedrich on 2016-02-24 23:32:19 +00:00

  • Relates set to 9060
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented May 11, 2016

Updated by gbeutner on 2016-05-11 14:08:36 +00:00

  • Status changed from New to Assigned
  • Assigned to set to gbeutner
  • Target Version changed from Backlog to 2.4.9
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented May 11, 2016

Updated by gbeutner on 2016-05-11 14:09:06 +00:00

  • Target Version changed from 2.4.9 to 2.4.8
@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented May 11, 2016

Updated by gbeutner on 2016-05-11 14:10:04 +00:00

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

Applied in changeset 1ad4d9c.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

commented Jul 6, 2016

Updated by tobiasvdk on 2016-07-06 07:48:08 +00:00

  • Relates set to 12035
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.