Network:
Nagios Bug and Feature Tracker
Bug and Feature Tracker
Main | My View | View Issues | Change Log | Roadmap
  

Viewing Issue Simple Details [ Jump to Notes ] [ View Advanced ] [ Issue History ] [ Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0000342 [Nagios Core] Check Scheduling major always 2012-06-02 05:04 2012-09-05 07:09
Reporter elisa View Status public  
Assigned To ageric
Priority normal Resolution fixed  
Status resolved   Product Version
Summary 0000342: Manually rescheduling a service check does not reset old timers
Description I have configured a service with check_interval and retry_interval both set to 60 and max_check_attempts to 26. This should give the service 26 hours to recover before entering a HARD state.

When triggering a WARNING by modifying the check_command the service will reschedule the next check to happen 60 minutes in the future. If I manually reschedule a check, then a check will happen and again, the next check will be scheduled to happen 60 minutes from there on. However, the already scheduled check will not be removed and will happen before 60 minutes have passed.

This happens for any manually scheduled service check. I've now rescheduled a check 3 times and hence get 3 additional service check results. The result is, that the service goes to HARD in less than 24 hours.

I've attached a screenshot of the relevant log entries showing the additional checks. I don't know if this also happens when the service is in OK, as the additional results would not show up in the log.
Additional Information
Tags No tags attached.
Nagios Version 3.4.1
OS Centos
OS Version 5.8
Attached Files ? file icon 2012-06-02-f6e3.bmp [^] (1,347,854 bytes) 2012-06-02 05:04
? file icon service.cfg [^] (1,001 bytes) 2012-06-02 05:08

- Relationships

-  Notes
(0000457)
elisa (reporter)
2012-06-02 05:09

 I attached the configuration of the service and its template.
(0000561)
ageric (administrator)
2012-09-05 07:09

 Most likely fixed by:

commit 5ab47acd67d45bc40d29f42173a91b5132055ba8
Author: Andreas Ericsson <ae@op5.se>
Date: Mon Sep 3 15:56:12 2012 +0000

    core: Make sure to stash next_check_event for hosts and services
    
    I stumbled on this by accident. It looked wrong and the fix is
    obviously correct, so we might as well apply it.
    
    Signed-off-by: Andreas Ericsson <ae@op5.se>
    
    git-svn-id: https://nagios.svn.sourceforge.net/svnroot/nagios/nagioscore/trunk@2138 [^] 5f96b256-904b-4d8d-8c98-d829582c6739

- Issue History
Date Modified Username Field Change
2012-06-02 05:04 elisa New Issue
2012-06-02 05:04 elisa File Added: 2012-06-02-f6e3.bmp
2012-06-02 05:04 elisa Nagios Version => 3.4.1
2012-06-02 05:04 elisa OS => Centos
2012-06-02 05:04 elisa OS Version => 5.8
2012-06-02 05:08 elisa File Added: service.cfg
2012-06-02 05:09 elisa Note Added: 0000457
2012-09-05 07:08 ageric Status new => assigned
2012-09-05 07:08 ageric Assigned To => ageric
2012-09-05 07:09 ageric Note Added: 0000561
2012-09-05 07:09 ageric Status assigned => resolved
2012-09-05 07:09 ageric Resolution open => fixed
2012-11-15 09:03 lftsy Issue Monitored: lftsy

Mantis 1.1.7[^]
Copyright © 2000 - 2008 Mantis Group
Powered by Mantis Bugtracker