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 #11825] Problems with check scheduling for HARD state changes (standalone/command_endpoint) #4232
Comments
Updated by mfriedrich on 2016-05-21 16:58:09 +00:00
We need to check whether a hardChange occurred when updating the next check. Using UpdateNextCheck() does not help here as it will include the scheduling offset. Testing a possible fix with a shorter interval range (check_interval = 60s, retry_interval = 30s).
|
Updated by gbeutner on 2016-05-23 08:38:36 +00:00
|
Updated by gbeutner on 2016-05-24 09:10:07 +00:00
Applied in changeset aeb7a4a. |
Updated by mfriedrich on 2016-05-24 11:21:00 +00:00
|
Updated by mfriedrich on 2016-08-08 11:14:28 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11825
Created by mfriedrich on 2016-05-21 16:51:25 +00:00
Assignee: gbeutner
Status: Resolved (closed on 2016-05-24 09:10:05 +00:00)
Target Version: 2.5.0
Last Update: 2016-08-08 11:14:28 +00:00 (in Redmine)
x. SOFT state -> retry_interval
HARD state -> retry_interval +1m (does not call UpdateNextCheck() in ProcessCheckResult())
HARD state -> ??? interval + 2m (seems to have been corrected with the 3m check_interval window from previous check; obviously called by ExecuteCheck/UpdateNextCheck)
HARD state -> check_interval +3m
2016-05-21 18:14:08 - {"check_result":{"active":true,"check_source":"mbmif.int.netways.de","command":["/usr/local/sbin/check_tcp","-H","","-M","warn","-p","10101","-r","crit","-t","10"],"execution_end":1463847248.8582880497,"execution_start":1463847248.8462469578,"exit_status":2.0,"output":"TCP CRITICAL - Invalid hostname, address or socket:","performance_data":[],"schedule_end":1463847248.8587419987,"schedule_start":1463847248.8419499397,"state":2.0,"type":"CheckResult","vars_after":{"attempt":1.0,"reachable":true,"state":2.0,"state_type":0.0},"vars_before":{"attempt":1.0,"reachable":true,"state":0.0,"state_type":1.0}},"host":"hard-interval","timestamp":1463847248.8593370914,"type":"CheckResult"}
2016-05-21 18:14:55 - {"check_result":{"active":true,"check_source":"mbmif.int.netways.de","command":["/usr/local/sbin/check_tcp","-H","","-M","warn","-p","10101","-r","crit","-t","10"],"execution_end":1463847295.3668069839,"execution_start":1463847295.3532509804,"exit_status":2.0,"output":"TCP CRITICAL - Invalid hostname, address or socket:","performance_data":[],"schedule_end":1463847295.3672609329,"schedule_start":1463847295.3500001431,"state":2.0,"type":"CheckResult","vars_after":{"attempt":2.0,"reachable":true,"state":2.0,"state_type":0.0},"vars_before":{"attempt":1.0,"reachable":true,"state":2.0,"state_type":0.0}},"host":"hard-interval","timestamp":1463847295.3680989742,"type":"CheckResult"}
2016-05-21 18:15:55 - {"check_result":{"active":true,"check_source":"mbmif.int.netways.de","command":["/usr/local/sbin/check_tcp","-H","","-M","warn","-p","10101","-r","crit","-t","10"],"execution_end":1463847355.3658659458,"execution_start":1463847355.3562619686,"exit_status":2.0,"output":"TCP CRITICAL - Invalid hostname, address or socket:","performance_data":[],"schedule_end":1463847355.3662919998,"schedule_start":1463847355.3500001431,"state":2.0,"type":"CheckResult","vars_after":{"attempt":3.0,"reachable":true,"state":2.0,"state_type":0.0},"vars_before":{"attempt":2.0,"reachable":true,"state":2.0,"state_type":0.0}},"host":"hard-interval","timestamp":1463847355.3669650555,"type":"CheckResult"}
2016-05-21 18:16:55 - {"check_result":{"active":true,"check_source":"mbmif.int.netways.de","command":["/usr/local/sbin/check_tcp","-H","","-M","warn","-p","10101","-r","crit","-t","10"],"execution_end":1463847415.3653900623,"execution_start":1463847415.3531889915,"exit_status":2.0,"output":"TCP CRITICAL - Invalid hostname, address or socket:","performance_data":[],"schedule_end":1463847415.3656980991,"schedule_start":1463847415.3500001431,"state":2.0,"type":"CheckResult","vars_after":{"attempt":1.0,"reachable":true,"state":2.0,"state_type":1.0},"vars_before":{"attempt":3.0,"reachable":true,"state":2.0,"state_type":0.0}},"host":"hard-interval","timestamp":1463847415.3662559986,"type":"CheckResult"}
2016-05-21 18:17:55 - {"check_result":{"active":true,"check_source":"mbmif.int.netways.de","command":["/usr/local/sbin/check_tcp","-H","","-M","warn","-p","10101","-r","crit","-t","10"],"execution_end":1463847475.372895956,"execution_start":1463847475.3587040901,"exit_status":2.0,"output":"TCP CRITICAL - Invalid hostname, address or socket:","performance_data":[],"schedule_end":1463847475.3730199337,"schedule_start":1463847475.3500001431,"state":2.0,"type":"CheckResult","vars_after":{"attempt":1.0,"reachable":true,"state":2.0,"state_type":1.0},"vars_before":{"attempt":1.0,"reachable":true,"state":2.0,"state_type":1.0}},"host":"hard-interval","timestamp":1463847475.3733570576,"type":"CheckResult"}
2016-05-21 18:19:55 - {"check_result":{"active":true,"check_source":"mbmif.int.netways.de","command":["/usr/local/sbin/check_tcp","-H","","-M","warn","-p","10101","-r","crit","-t","10"],"execution_end":1463847595.3624830246,"execution_start":1463847595.352396965,"exit_status":2.0,"output":"TCP CRITICAL - Invalid hostname, address or socket:","performance_data":[],"schedule_end":1463847595.362817049,"schedule_start":1463847595.3500001431,"state":2.0,"type":"CheckResult","vars_after":{"attempt":1.0,"reachable":true,"state":2.0,"state_type":1.0},"vars_before":{"attempt":1.0,"reachable":true,"state":2.0,"state_type":1.0}},"host":"hard-interval","timestamp":1463847595.3629999161,"type":"CheckResult"}
2016-05-21 18:22:55 - {"check_result":{"active":true,"check_source":"mbmif.int.netways.de","command":["/usr/local/sbin/check_tcp","-H","","-M","warn","-p","10101","-r","crit","-t","10"],"execution_end":1463847775.3754639626,"execution_start":1463847775.3603029251,"exit_status":2.0,"output":"TCP CRITICAL - Invalid hostname, address or socket:","performance_data":[],"schedule_end":1463847775.3755888939,"schedule_start":1463847775.3500001431,"state":2.0,"type":"CheckResult","vars_after":{"attempt":1.0,"reachable":true,"state":2.0,"state_type":1.0},"vars_before":{"attempt":1.0,"reachable":true,"state":2.0,"state_type":1.0}},"host":"hard-interval","timestamp":1463847775.3759551048,"type":"CheckResult"}
Log from over here: https://monitoring-portal.org/index.php?thread/36174-wrong-retry-interval-check-interval-switching/
Changesets
2016-05-21 16:58:19 +00:00 by mfriedrich d49b63d
2016-05-24 09:05:29 +00:00 by gbeutner aeb7a4a
2016-05-24 10:42:02 +00:00 by gbeutner 7b371f2
Relations:
The text was updated successfully, but these errors were encountered: