Skip to content
This repository has been archived by the owner. It is now read-only.

[ #300] fix sending two identical service_status events to neb module #127

icinga-migration opened this issue Feb 23, 2010 · 1 comment


Copy link

@icinga-migration icinga-migration commented Feb 23, 2010

This issue has been migrated from Redmine:

Created by mfriedrich on 2010-02-23 14:10:19 +00:00

Assignee: mfriedrich
Status: Resolved (closed on 2010-02-23 14:15:06 +00:00)
Target Version: 1.0.1
Last Update: 2010-02-23 14:15:06 +00:00 (in Redmine)

from nagios-devel

-------- Original Message --------
Subject: Re: [Nagios-devel] Host and Services update fonction called twice
Date: Tue, 23 Feb 2010 14:12:24 +0100
From: Andreas Ericsson <>
Reply-To: Nagios Developers List <>
To: Nagios Developers List <>
References: <> <> <> <> <> <> <> <> <> <>

On 02/22/2010 04:51 PM, Matthieu Kermagoret wrote:

On Fri, May 15, 2009 at 11:55 AM, Matthieu Kermagoret
<> wrote:
> This issue has been successfully reproduced on Nagios 3.0.6, 3.1.0 and
> the latest CVS revision with NDOUtils 1.4b7.

Can still be reproduced with latest Nagios CVS revision. This is now
the oldest unassigned issue within Nagios' tracker
( :-(

You'll find attached a patch which tries to correct Nagios' behavior.
It causes host/service status not to be updated when check is
scheduled but only when check results are processed. Is there any
weird case that would cause this logic to fail ?

The patch seems correct, but the description of it isn't. Status
updates should take place whenever there is a modification to the
state of the service. This is important, since a GUI needs the
next_check information (and suchlike) to properly draw the scheduling
queue. Such updates should ofcourse only come once, so this patch
is still correct.

Will apply. Thanks.


2010-02-23 14:14:24 +00:00 by mfriedrich 9a0d5ba

fix sending two identical service_status events to neb module

fixes #300

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Feb 23, 2010

Updated by mfriedrich on 2010-02-23 14:15:06 +00:00

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

Applied in changeset commit:"9a0d5baff02fd76f477d5634dccc2700a0c228a9".

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.