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 #8805] check cluster-zone returns wrong log lag #2568
Comments
Updated by gbeutner on 2015-03-19 07:44:05 +00:00
Can you show me the output of "ntpdate -q pool.ntp.org" on both of your masters? |
Updated by rhillmann on 2015-03-19 08:11:18 +00:00 master-1
master-2
|
Updated by mfriedrich on 2015-03-26 16:22:19 +00:00
|
Updated by smadmin on 2015-04-10 13:13:21 +00:00 We can confirm this:
|
Updated by dgoetz on 2015-07-03 06:57:23 +00:00 Perhaps some hints on the problem, I found while playing with this check:
|
Updated by bfek-18 on 2015-07-16 14:01:34 +00:00 The problem is in version 2.3.7 still available. |
Updated by mfriedrich on 2015-07-23 10:30:04 +00:00
|
Updated by mfriedrich on 2015-07-24 18:12:18 +00:00
|
Updated by tgelf on 2015-09-09 09:29:57 +00:00 2.3.10, issue persists. |
Updated by mfriedrich on 2015-09-09 10:45:21 +00:00
|
Updated by mfriedrich on 2015-09-25 12:23:11 +00:00
When the remote endpoint log position is 0, the lag difference is the current time which results in that output formatting. FixRefactor the calculation into a function, since we use that for 2.4 inside the api status queries. Makes back porting harder, but who cares anyways. TestsModified icinga2b's log position to 0, unpatched output: Applied Fix |
Updated by mfriedrich on 2015-09-25 12:25:04 +00:00
Applied in changeset 717118f. |
Updated by mfriedrich on 2015-09-25 12:37:24 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/8805
Created by rhillmann on 2015-03-18 21:52:10 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2015-09-25 12:25:04 +00:00)
Target Version: 2.3.11
Last Update: 2015-09-25 12:37:24 +00:00 (in Redmine)
Since update to r2.3.0-1 the check "cluster-zone" displays the log lag.
In our envirenoment we watched the issue that the log lag seems not be correct:
Zone 'master' is connected. Log lag: 6 days, 14 hours, 7 minutes and 4 seconds
We have continously icinga2 service reloads, every 20min caused by puppet, but the log lag is still "behind" on our two master servers. We have seen the same problem on the other zones.
The file /var/lib/icinga2/api/log/current has current has current timestamp and icinga is continously writing on it. I am not sure how the api client gets the current log position, but it seems to be wrong in some cases.
My zone.conf
Attachments
Changesets
2015-09-25 12:24:45 +00:00 by mfriedrich 717118f
2015-09-25 12:28:01 +00:00 by mfriedrich c3a4744
Relations:
The text was updated successfully, but these errors were encountered: