Percy Jahn wrote:
> Hello,
>
>
>> If nagios got outstanding
>> checks while receiving "disable notifications" it sets the global status
>> accordingly. reap_service_checks() gets the check results from the
>> outstanding properly scheduled service checks and trys to reschedule the
>> servicecheck via schedule_service_check(). This function immediately
>> exists without rescheduling, because active checks are disabled globaly.
>> In the end, the service is lost and could not be rescheduled.
>> check_for_orphaned_services() could not solve this problem, because the
>> check is marked as "not executing/running" by reap_service_checks().
>>
>
>
>
> This problem still exists, is nobody interested in this Bug? In my
> opinion this is a serios problem. If i click on "stop executing active
> checks" and after a short while "start executing active checks." there
> are checks that never get scheduled, until i restart nagios?
>
> I only need to know, if the suggested solution of changing
> schedule_service_check to reschedule inactive checks to, would break
> anything.
It shouldn't.
> If not i could submit a patch these days. Otherwise i have to
> spend some more hours investigating the problem.
>
Submit the patch with some testing data and I'll have a look at it. It's
been a while since I mucked around with the Nagios code, but I'll make
provided your changes are minimal it shouldn't be too hard to oversee
any side-effects it might cause.
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]